15 ms·
Depending on the amount of write throughput you need and whether you care about latency, "concurrent writes" aren't necessarily a problem either. You can just s
by kevingadd 2y ago
Depending on the amount of write throughput you need and whether you care about latency, "concurrent writes" aren't necessarily a problem either. You can just shove them into a queue and then have a single thread pull stuff out of the queue and push it into SQLite. That still scales, up to a point.
- dinosaurdynasty 2y agoFYI this is basically what Redis does (which does not support concurrent writes or reads afaik), and that still scales quite a lot.
- immibis 2y agoNo, because your readers are still blocked by writers and still randomly fail if you forgot to set busy_timeout, which is something at least one person didn't they had to do until they read this comment.
- emseetech 2y ago| readers are still blocked by writers We're all using WAL mode these days, right?