We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WAL mode for Sqlite is significantly faster and more resilient than the default methode, especially on modern filesystems like Btrfs, see: https://wiki.tnonline.net/w/Blog/SQLite_Performance_on_Btrfs
Would be nice if this could be used by default.
Thanks!
The text was updated successfully, but these errors were encountered:
more resilient it is not, speed? Depends on what you do. The trade offs are enumerated in the sqlite docs quite well.
WAL might be a good for for us though, considering we are mostly append only and write heavy.
The EBUSY stuff could be interesting and we'd need to catch that in the db and retry accordingly
Sorry, something went wrong.
No branches or pull requests
Feature Description
WAL mode for Sqlite is significantly faster and more resilient than the default methode, especially on modern filesystems like Btrfs, see: https://wiki.tnonline.net/w/Blog/SQLite_Performance_on_Btrfs
Would be nice if this could be used by default.
Thanks!
The text was updated successfully, but these errors were encountered: