how many db queries per user on 1 page?

mega_hurtz

Hey guys, since they are many developers out there, I want to get a estimated number of times that I could hit mysql with queries and not feel degradation when the user requests a single page.

If any of you have developed any web apps, please reply and let me know how many queries you've used to generate a page. As it stands, my web app will be hitting mysql with 4 or 5 queries for a single page. (simple select from where statements.) Did I over do it, or am I just being too kind to the system. I am expecting about 500-1000 hits per day starting off, and we will temporarily be running on two servers. (1 web, 1 db). This is an e-commerce application.

I'd appreciate hearing from you. Thanks.

Anon

With such a few number of hits, you should be fine. It's quite a lot of queries but for only 500-1000 views a day that's nothing. For that, you don't even need two servers.

amcgrath

you prolly don't need the db server, true, but i'd keep it exactly like you got it. Brian's right too, 500-1000 is nothing at all, so i wouldn't worry about that. If you see slowness, really look at the code efficiency before thinking it's a mysql thing (I use postgres, btw so I can't comment past that).

Anon

thanks guys, I'll keep this in mind.

Anon

It's not the number of queries, but the efficiency of them all together. If you're just doing simple single table selects, and throwing it on the screen, dozens are ok. If you're doing a complex union / join / subselect thing, it could get ugly quick.

edwardsbc

My experience is quite the opposite. I have replaced many single "simple" queries with fewer complex queries utilizing JOINs and subqueries. In all these cases, where the information displayed was the same in both cases, the complex query returned much faster. You have to remember the overhead of connecting to the database and issuing a query and passing the result cursor. My experience is with MS SQL 7, so your mileage may vary.