[eluser]Colin Williams[/eluser]
I personally start biting my nails at like 15 But I don't know the actual answer. I mean, you could have one ridiculously large query and that would be bad. Tools like Drupal have 100+ out of the box. I'd be interested to hear from more experienced developers as well.
[eluser]Glen Swinfield[/eluser]
You need to use as many as you need to use. It is just important to make sure that you are not running the same query twice where it is not necessary, and your sever etc is tuned to handle it.
If you limit yourself to a specific number without any wider consideration, you are effectively limiting what it is possible to build.
[eluser]Bramme[/eluser]
[quote author="Glen Swinfield" date="1218898308"]It is just important to make sure that you are not running the same query twice where it is not necessary.[/quote]
Yeah, that's pretty important. I developped a site a while back, when I turned on the profiler, I suddenly saw I was doing some identical queries two or three times per page. Some caching and some smarter coding fixed that problem quickly, halving the amount of queries I had on my pages...
[eluser]Derek Jones[/eluser]
The number of queries is a poor indicator of database usage optimization since all queries are not created equal. You could write one bad SELECT query that took the same time and more memory to retrieve than 1000 indexed COUNT queries.
But I don't know the actual answer. I mean, you could have one ridiculously large query and that would be bad. Tools like Drupal have 100+ out of the box. I'd be interested to hear from more experienced developers as well.
