3 ms·
a. I'm surprised no one has mentioned WAL2 + BEGIN TRANSACTION, both of which are in separate branches with the plan to be merged into main. Even though SQLite
by alberth 5y ago
a. I'm surprised no one has mentioned WAL2 + BEGIN TRANSACTION, both of which are in separate branches with the plan to be merged into main.
Even though SQLite can handle 99% of peoples use cases, WAL2 + BEGIN TRANSACTION will greatly close that last 1% gap.
b. Expensify has created a client/server database based on SQLite called https://bedrockdb.com https://bedrockdb.com and years ago it was scaling to 4M+ qps https://blog.expensify.com/2018/01/08/scaling-sqlite-to-4m-qps-on-a-single-server/ https://blog.expensify.com/2018/01/08/scaling-sqlite-to-4m-q...
- Jason_Gibson 5y agoDo you mean 'BEGIN CONCURRENT'? https://sqlite.org/cgi/src/doc/begin-concurrent-pnu-wal2/doc/begin_concurrent.md https://sqlite.org/cgi/src/doc/begin-concurrent-pnu-wal2/doc... Where did you see that the plan is to bring those into the mainline distribution?
- alberth 5y agoWhoops, yes - meant BEGIN CONCURRENT (I can't update my original post).
- ngrilly 5y agoI wasn’t aware or a plan to merge wal2 and BEGIN CONCURRENT into main. That would be awesome. What is your source about this?