3 ms·
> the performance criticism of SQLite is vastly overblown That kind of depends on how you use it. Obviously this depends on the row size, constraints, etc., bu
by DrJokepu 10y ago
> the performance criticism of SQLite is vastly overblown
That kind of depends on how you use it. Obviously this depends on the row size, constraints, etc., but if you want to write more that a few thousand rows per second for longer periods, the performance limitations of SQLite will become very obvious very quickly.
- creshal 10y agoWhen your little side business needs to more than a few thousand rows per second for longer periods, you're either having enough customers to justify migration, or have the most inefficient database scheme of the decade.
- DrJokepu 10y agoNot every piece of software that needs to store data is a CRUD application and "little side businesses" are not the only use cases for an embedded database. For example, an embedded application logging readings from a number of sensors could easily reach thousands of writes per second. Another example would be a desktop (or mobile) email client such as Apple Mail using SQLite to store data, it could easily reach thousands of writes per second when e.g. downloading the entire mailbox from an IMAP server.
- nilved 10y agoCertainly true. I'm not saying that SQLite is always the best choice. But people like to say "SQLite is not performant" when they really mean "SQLite is not performant for concurrent-write-heavy applications" which is a small minority. In most but not all cases the performance of SQLite is perfectly adequate.