54 million visits per day on a VPS?More stress testing the VPS with scripts since nobody’s volunteered a real site. Just running a couple scripts continually downloading the tracker image from the VPS, it seems to be handling 2000-3000 queries per second on the database while extremely responsive. Either something’s wrong or I underestimated just how little resources you need when you have few enough users on a server that all the tables can be kept in memory. If only W3Counter’s database server had 24GB of RAM…
Tags: database server, RAM
 |
Self-promotion
Recent Comments
Activity Stream
Popular Posts
|
  |
|
|||
Home About Archives Projects Links
|
October 27th, 2007
I wouldnt have thought a VPS could handle that…heck, there are some dedicated servers that would struggle with that!
October 27th, 2007
Left it all running overnight and now getting ~800 queries per second. I thought VPS’s got equal shares of the physical server CPU… maybe not. Maybe there was just no load at 4AM on a Friday night… regardless, this seems more than enough to handle even pretty darn large sites.
October 27th, 2007
The impression I’ve gotten in the past when looking at VPS packages is that you get a guaranteed portion of the physical machine’s CPU, and any remaining can be eaten into if the other divisions on the server aren’t using it (ie: if they want to use it, they’ll be prioritised above you).
RAM is often treated in the same way, with you getting an allotted amount and there being the option to burst to higher amounts if it’s free.
This is pretty much the defining difference between a VPS and a dedicated server, as the latter removes this level of unpredictability — something that also affects shared hosting.
November 16th, 2007
what did you mean by volunteer a real site?