2 ms·
I think the way it's worded in that SQLite documentation page is still accurate: > SQLite supports an unlimited number of simultaneous readers, but it will onl
by simonw 5y ago
I think the way it's worded in that SQLite documentation page is still accurate:
> SQLite supports an unlimited number of simultaneous readers, but it 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. But there are some applications that require more concurrency, and those applications may need to seek a different solution.
If your application needs to support hundreds of concurrent writes a second you shouldn't use SQLite. But that's a pretty high bar!
- zoomablemind 5y agoAlso it should be noted that SQLite is a library, so it charges against the quotas for the main process. This may become an issue with large run-time datasets even in read-only shared access scenarios.