6 ms·
It is only good if you do few writes, with at least seconds in between.
by Euphorbium 4y ago
It is only good if you do few writes, with at least seconds in between.
- warmwaffles 4y agoWrong. SQLite can handle concurrent writes using a WAL. You do not have to wait any amount of time between writes. Once the write is done, it is done.
- daneel_w 4y agoDid you evaluate SQLite on a floppy drive or something?
- Glench 4y agoIncorrect. Here are some actual numbers: https://blog.wesleyac.com/posts/consider-sqlite https://blog.wesleyac.com/posts/consider-sqlite > Writing 512 byte blobs as separate transactions, in WAL mode with synchronous=normal3, temp_store=memory, and mmap enabled, I got 13.78μs per write, or ~72,568 writes per second.
- Euphorbium 4y agoGo on, trust the metrics. It locked up every time I had to do many writes without delay.
- Glench 4y agoNot sure what your experience is but I'm running SQLite in my production web app and it's just fine :)
- markusw 3y agoThen you did something wrong. SQLite has phenomenal performance for many workloads: https://www.golang.dk/articles/benchmarking-sqlite-performance-in-go https://www.golang.dk/articles/benchmarking-sqlite-performan...