News for hackers. Stuff that matters.
Re:SQLite 3.8.0 Release with next-generation query planner by eurleif on Tuesday August 27, 2013 @04:08AM (#6282121)
Presumably there were many SELECTs for every INSERT.
Re:SQLite 3.8.0 Release with next-generation query planner by eksith on Tuesday August 27, 2013 @04:48AM (#6282252)
Yes. Yes there were. :)

We always limited transactions for UPDATES and INSERTs that involved more than one table.

It was quite the learning experience since you do have to think of different ways of working with data. You get to learn very quickly the difference between what like to store vs. what you actually need to store to get a particular functionality. But that turned to being a boon in the end because we got a much simpler forum as a result. Fewer bells and whistles meant users focused on actual discussion and not ancillary, shiny bits and bobs.

Re:SQLite 3.8.0 Release with next-generation query planner by vidarh on Tuesday August 27, 2013 @05:22AM (#6282372)
But on a machine with 2GB of RAM running a forum that small, pretty much none of those selects should ever need to hit disk - it should all pretty much be in the buffer cache, unless there were lots of full text searches of the entire posting history.

EDIT: And that is without any app specific caching.