undefined | Better HN

0 pointsledgerdev3y ago0 comments

Here's sqlite doing 100 million inserts in 33 seconds which should fit into nearly every workload, though it is batched. https://avi.im/blag/2021/fast-sqlite-inserts/

So write contention from multiple connections is what you're talking about, versus a single process using sqlite?

0 comments

lvass3y ago

Keyword here is transactions, not processes. You can model any workload to be transaction-efficient, but it might not be easy.

No durability guarantee is a showstopper for any serious use case

Not sure what you mean by durability. Sqlite has WAL that can be replicated (see litestream)

If it's good enough for avionics and nuclear subs, it's probably good enough for most web apps.

Web apps do more concurrent writes than subs, plus you can configure SQLite for more durability

That's correct, I meant the many cores to allude to many processes.

j / k navigate · click thread line to collapse