Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This question already has an answer here:

I'm curios what's the traffic a dual-socket CPU server machine can handle? Just hypothetical, does anybody have a clue what are the keystones? Is it more about hardware or connection or anything else that should be taken in consideration?

Let's say something like that
and AMD Opteron 6300 .

I'm a total newbie so pardon me if I'm missing something.

Appreciate your info sharing, BR

share|improve this question

marked as duplicate by joeqwerty, mdpc, Michael Hampton, EEAA, Iain Mar 26 '13 at 6:41

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

Problem with these kind of question is that even a hypothetical scenario isn't really conceivable. The ends are just so far apart, it's hard to say anything.

Assuming the bandwidth is not an issue, if you take a pure html website, a single celeron from years past will have no problem serving millions and millions of requests. Comparatively, a faulty or even a very heavy processing script could take ages to complete a single request. So, the single greatest factor is the question of what you are running on the server.

You can use benchmarks to relatively compare one system against another in certain aspects. But even benchmarks can't tell you anymore than that.

If you want to be in a position where you can make numerical estimates of how much you can handle, you will need to run your application under load (test) and make expectations from it. That is the only way. That is, benchmark it against your application.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.