Hi everyone, Im setting up a db driven website with lots of dynamically changing data, and pretty much ZERO static web pages.
I just got my first dedi server up and running, and was wondering, in terms of “How many requests per second” that my server can deal with, what is reasonable figure to have?
I am confused because:?
Lots of people say “Oh, if u have a static web page, u can serve 1000 requests per second, and survive a slash dot effect”
Or lots of people say “Oh, dont worry, a single box can handle a busy forum site with 1000 simultaneous users.”
The problem is
Im not serving Static Pages, and currently im not getting ANYWHERE EVEN NEAR 1000 requests per second.
1000 simultaneous users on a forum is a pretty useless metric, because it doesnt really tell how much ur server can serve! You could have 1000 simultanenous users in a forum, but on average, only 10 load a page every second. So that would mean the server would only need to handle 10 page requests a second.
So, does anyone have any idea what is a reasonable amount of pages served a second, that a single dynamic server should be able to handle?
Just ball park figures please… Like 1 page a second, 10 page a second, etc etc.
It depends how many resources a webpage takes to serve. If your page requires 100 database queries, you’re probably not going to serve as many simultaneous pages as a static site with none. You may not be able to serve 1 page per second, or you may be able to serve thousands. When I said there was no way to ballpark this I meant it. You need to talk about a specific application (like a website you created) and test it.
Few definitive numbers   exist regarding the precise magnitude of the Slashdot effect, but estimates put the peak of the mass influx of page requests at anywhere from several hundred to several thousand hits per minute.