[xiphias2]

It's a bit strange that SQLite went up only 1 place on the ranking (to the 10th).

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.

[jabwd]

SQLite performance is kinda nutty. My design of the DB at the time was probably poor (but I was 15 so cut me some slack :D) but I made an app that had to run on iPod Touches at the time, so we could use the accelerometer for physics class in school.

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.

[cpursley]

Don't get me started on Rails and all the anti-patterns that Active Record introduces...

[xiphias2]

You don't have to. I believe RoR has good and bad sides, but the multi-threaded debugging stories of _why_ there were timeout problems when the interpreter got a global interpreter lock and how SQLite driver got fixed translates to lots of other programming languages.

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.