Avinash Sajjanshetty's blog on SQLite performance, database storage architecture, checksums, and bloom filters.
HN links it for fast SQLite insert benchmarks and the post noting SQLite lacks checksums; one commenter calls other posts hype-heavy, another disputes that.
> There are plenty of large projects written in Python.
There are, but they are certainly a pain in the ass to work with.
I once had to work on a semi-large Python codebase and got so frustrated that I wanted to port the code to some other language. The best part? I wrote the majority of that codebase myself, just months earlier.
I ranted about it here: https://avi.im/blag/2023/refactoring-python/
> I'd personally prefer deeper thinking which this blog's previous posts-- high in hype and low in technical rigor-- have not yet provided.
Really? Something like this[1] (literally the previous post made by the author!) is "high in hype and low in technical rigor"? Or do you just have an axe to grind?
[1]: https://avi.im/blag/2024/sqlite-past-present-future/
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?
SQLite has it's own issues - for example it doesn't support checksums. Quite bizarre for a database file format where integrity is supposedly highly valued.
With a zip file at least you know your file was corrupted.
https://avi.im/blag/2024/sqlite-bit-flip/