Pre-optimization is the root of all evil.
I’ve been working hard on Stencyl’s new CMS system, which will hopefully see a release tomorrow or Thursday, and as part of that, I’ve been working on the classes that allow page editing. I have discovered the truth in the old adage that forms the title of this post; Though it may not be entirely correct to have 15 SQL queries on a single (editing) page, you know what? I use an application daily that has 55 (mind-boggling queries) on its index page, regardless of who is accessing it. The server hasn’t died under load much greater than Stencyl’s. If I have 15 queries to change a page’s information once upon a time, I’m gonna keep it that way until it becomes a problem.
Of course, I pre-optimized the crap out of the frontend so it uses a max of 4 queries on an ordinary page view and something like 8 once a day to refresh the cached information.
Tally ho then, it’s back to work.