Depends on your website performance. Every hosting provider has things set up slightly differently. Mine has a different server running the MySQL instance than the apache/php box — so each query has to go out over the internal network to get processed. At home, everything is on one machine, so it goes through a null-pipe to talk to the SQL service.
My belief is that around two dozen is pretty good if you are running a few useful plugins. Beel is going to be my ‘test optimization’ case over time, to see if I can help him come down a bit more (though I >was< part of the problem at one point!). Caching is key, as is not doing queries you don’t really have to, and requesting all the data you can rather than a secondary query later.
Of course, there’s the inevitable tradeoff of asking for too much data, which takes longer to process and send back on the wire, versus asking for minimal data and thus needing a second/followup query to fill in the blanks.
At the end of the day, if your page loads fast enough for you, and your hosting provider isn’t bitching about you taking a hit on their SQL server, you’re okay with a few dozen certainly, more in certain circumstances (i.e., I have administrative scripts which run hundreds of queries on a given page…).
-d
CHAITGEAR
