3 ms·
> SQLite definitely seems like a poor choice for dealing with many concurrent requests Can you qualify "many"? SQLite easily handles 100k+ writes per second an
by wild_egg 3mo ago
> SQLite definitely seems like a poor choice for dealing with many concurrent requests
Can you qualify "many"? SQLite easily handles 100k+ writes per second and it's not hard to have app layer code serialize and batch writes to take advantage of that speed. Concurrent writes require a ton of overhead and your system and code can be quite a lot faster and simpler if you just skip the idea of them altogether.
- inigyou 3mo agoSQLite serialises all writes - only one can proceed at a time and others must wait until that one is finished
- victorbjorklund 3mo agoWrites are fast unless you are doing some complex transaction stuff.
- inigyou 3mo agoEach one includes a few fsyncs