33 ms·
Honestly, if you care about that level of concurrency, it begs the question of why are you using an in process database in the first place?
by bawolff 10mo ago
Honestly, if you care about that level of concurrency, it begs the question of why are you using an in process database in the first place?
- miohtama 9mo agoOne reason is that architecture and maintenance are much simpler
- sealeck 9mo agoIt's not just about performance: having an in-process MVCC engine would simplify the implementation of many single-machine concurrent applications. Currently you usually have to combine SQLite with some kind of concurrency primitives; this is extremely painful because most OS-level concurrency primitives are really easy to misuse (e.g. it's trivial to accidentally add deadlocks, and very hard to spot and remove these ahead of time: example hard to spot concurrency bugs https://fly.io/blog/corrosion/ https://fly.io/blog/corrosion/, https://rfd.shared.oxide.computer/rfd/400 https://rfd.shared.oxide.computer/rfd/400)