Exceeding 50,000 SQL querries per hour

Exceeding 50,000 SQL querries per hour

by Andrew Palmer -
Number of replies: 3
In the last two days we have had our SQL database server shut down our site, because we have a 50,000 querries per hour limit.  This is a commercial provided server and is shared.  At the time of the crash there were only aproximately 20 users online taking quizes.  Obviously using PHP has advantages, but now I'm seeing the downside.  It appears we will have to upgrade our service to a virtual server with unlimited querries unless anyone knows another solution.
Average of ratings: -
In reply to Andrew Palmer

Re: Exceeding 50,000 SQL querries per hour

by Randy Obert -

I would find a new home for your account...

This is a typical "get what your pay for" issue. As is often the case today, we see a large number of upstart hosts offering services well below the actual costs of providing them. This is because most clients never get near these unrealistic limits.  When a client starts to create some traffic, the host either gives you your walking papers or imposes limits like this.

Average of ratings: -
In reply to Andrew Palmer

Re: Exceeding 50,000 SQL querries per hour

by Visvanath Ratnaweera -
Picture of Particularly helpful Moodlers Picture of Translators
Quizes consume lot of ressources. Still 2500 SQL querries per user sound a little high. Can anybody confirm the order of these numbers?

About your next option "virtual" server: Is it a virtual server as Apache understands it (one physical server, one Apache instance responding to different domain names) or a virtual machine (a physical server devided into comparments).

In the first case each server can go upto the peak performance of the physical machine, provided of course, the other virtual servers are idle. In the second case each virtual machine is capped.

Dedicated servers (one physical server for you alone) is not that expensive these days.
Average of ratings: -