3 ms·
SQLite loses most of its edge in concurrent write scenarios, but its read performance is difficult to beat. A lot of it comes from what TFA says: there's no ne
by Uberphallus 6y ago
SQLite loses most of its edge in concurrent write scenarios, but its read performance is difficult to beat.
A lot of it comes from what TFA says: there's no network roundtrip, but a function call. Even in a local machine, a unix socket query will carry at least a couple of system calls with potential context switches, and that makes regular RDBMS lag behind when you do tons of sequential and small queries.
Of course, when you have large results or complex queries that eat a bigger chunk of the time cake and that technical advantage wanes. After that, which RDBMS has the performance lead is largely workload-dependent.