> SQLite can max out my NVMe drives, despite its internal serialization constraint. Do you have a (write) benchmark which demonstrates that? Is this many compe

> SQLite can max out my NVMe drives, despite its internal serialization constraint. Do you have a (write) benchmark which demonstrates that? Is this many competing small transactions (as in a typical web workload)? Or buffering multiple writes into fewer but larger transactions? I'm more positive on the latter, but of course it changes the semantics somewhat. SQLite itself says this [1]: "[SQLIte] will only allow one writer at any instant in time. For many situations, this is not a problem. Writers queue up. Each application does its database work quickly and moves on, and no lock lasts for more than a few dozen milliseconds." Synchronizing on one lock hold for dozens of ms is a big issue for processing large number of concurrent writes, so I'm curious how you've solved this in your application. [1] https://www.sqlite.org/whentouse.html https://www.sqlite.org/whentouse.html