sqlite supports concurrent access. It's optional, though. It also requires help from the os/file system (that's usually only an issue in specific contexts). So

sqlite supports concurrent access. It's optional, though. It also requires help from the os/file system (that's usually only an issue in specific contexts). So... you can get your ducks in a row in terms of checking sqlite docs, your sqlite config and compile-time options, and your runtime environment, and then remove the mutexes (modernc is another variable, but I don't know about that). Or, if it's working for you, you can leave them in. Reasons to remove them might be... it's a pain to maintain them; it might help performance (sqlite is inherently one writer multiple readers, and since you're using RW locks, your locks may already align with sqlite's ability to use concurrency). If those aren't issues for you then you can leave them in.