There's a lot of new articles of how to improve its performance and I love that I don't have to care about the n+1 problem so much.
It is now the default production database for Rails for a good reason.
There's a lot of new articles of how to improve its performance and I love that I don't have to care about the n+1 problem so much.
It is now the default production database for Rails for a good reason.
initially the performance was too poor, but after a bunch of reading and some changes in how I was using SQLite I got it to easily do more than 100k rows per second of insertions (the db wasn't very wide). On an old embedded device, mind you. Didn't need that much, but wowza! was my expression at the time. I've had a love for it in my heart every since.
Just saying that you run network I/O and blaming the kernel / network latency for all the delays in other SQL drivers is easy, but with SSDs getting so much lower latency than HDDs, one has to seriously consider throwing out network based databases for lots of programming tasks.