SQLite on Rails: The how and why of optimal performance
fractaledmind.github.io
SQLite on Rails: The how and why of optimal performance
1–10 of 98 posts
Re: SQLite on Rails: The how and why of optimal performance
#2This is a really long blog post to just say that you should turn on the WAL if you want concurrency out of SQLite. All the other stuff is superfluous.
Re: SQLite on Rails: The how and why of optimal performance
#3This is a really long blog post to just say that you should turn on the WAL if you want concurrency out of SQLite. All the other stuff is superfluous.
Can't agree.
I learned about BEGIN IMMEDIATE TRANSACTION.
And there's also busy_timeout.
The article also explains why/how/when things occur in detail which is valuable.
Re: SQLite on Rails: The how and why of optimal performance
#4I can't imagine how many days the author took to write such detailed article.
This is useful to anyone trying to scale SQLite web applications, even beyond Rails.
So thank you!
Re: SQLite on Rails: The how and why of optimal performance
#5This is a really long blog post to just say that you should turn on the WAL if you want concurrency out of SQLite. All the other stuff is superfluous.
I thought it was a pretty good list of common Rails-application-specific and sqlite3-specific knobs to turn, for newcomers to performance tuning. (Really just a guided tour though -- turn this knob to enable this particular tool for dealing with concurrency problems...)
Re: SQLite on Rails: The how and why of optimal performance
#6This is a really long blog post to just say that you should turn on the WAL if you want concurrency out of SQLite. All the other stuff is superfluous.
[deleted]
Re: SQLite on Rails: The how and why of optimal performance
#7much easier just to use pg
Re: SQLite on Rails: The how and why of optimal performance
#8much easier just to use pg
Not really. Setting a few sqlite options and enabling litestream for backups is much easier than setting up Postgres with reliable backups.
Should you do this for all apps? No. Do you have read heavy applications? Consider SQLite
Re: SQLite on Rails: The how and why of optimal performance
#9So this is Rails + Litstream, cool!
Re: SQLite on Rails: The how and why of optimal performance
#10much easier just to use pg
I'm not using Rails, but I now have several sites using my own little thing that is a single docker container where all state + content is in a single sqlite file, and it's very nice to be able to just move that single file around. I love postgres, but doing the equivalent of that with Postgres is a lot more hassle.