Multi-threaded SQLite without the OperationalErrors (2017)

Re:Multi-threaded SQLite without the OperationalErrors (2017) by lacampbell on Thursday May 30, 2019 @07:11PM (#20056877)

I'd be interested to hear as much about your set up as you can divulge. How many concurrent writing users you have, you use a cache, etc.

> In terms of management, SQLite absolutely cannot be beaten. It is literally as easy as copying any other file when performing backups or restores.

This - I have a lot of respect to DBAs, enough to know that I am not one.

[ Parent | on HN ]

Re:Multi-threaded SQLite without the OperationalErrors (2017) by tracker1 on Thursday May 30, 2019 @08:22PM (#20057227)

Can't speak for GP, but it really will vary on workload. How much data is in each DB, how much workload is write vs read. In a mostly read scenario (say a blog), I'd be surprised if you couldn't handle 100k simultaneous users on a fast drive, more with a good caching strategy.

For modest read/write, should be able to get 1000-10k users without much issue.

A little advice would be to ensure logging is to a separate db/drive from the main data if you are logging changes, etc.

The only down side is distribution with High Availability, but so many scenarios don't actually demand the extra overhead for true HA.

[ Parent | on HN ]