| ▲ | andersmurphy 5 days ago | |
Not sure what you are talking about? In WAL mode (which is what you should be using) writes don't block reads and reads don't block writes. If you are connections pooling (which you should) the cache will stay hot. Sqlite (properly configured) will outperform "proper databases" often by an order of magnitude in the context of a single box. You want a single writer for high performance as it lets you batch. > 256 hardware threads... Have you tried? I have. Others have too. [1] > Additionally, SQLite lacks a bunch of integrity checks, like data types and various kinds of constraints. And things like materialised views, etc. Sqlite has blobs so you can use your own custom encoding which is what you want in a high performance context. Here's sqlite on a 5$ shared VPS that can handle 10000+ checks per second over a billion checkboxes [2]. You're gonna be fine. - [1] https://use.expensify.com/blog/scaling-sqlite-to-4m-qps-on-a... | ||