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

I am hosting a big campaign that is going to launch tomorrow. The expected avg. number of visits on the first day is +200 000 users. Assuming everyone is going to visit 5 pages on avg., this makes 1 000 000 views x 20 static files, 20 000 000 requested.

The server I am using is:

Processor: Intel Core i5-2400 4x3.1+ GHz 6 MB L2 - QPI 5 GT/sec
Virtualisation: VT Instructions
Turbo Boost Technology: @ 3.40GHz
Architecture: 64 bits
Hard disk: Intel SSD 320 (2x 120 GB)
NIC: FastEthernet
SwitchPort: 100 Mbps

The script itself doesn't involve many MySQL requests or complex PHP operations. Using HTTP server.

Should I upgrade my server or should this be enough to handle the traffic?

share|improve this question

closed as too localized by Bart De Vos, Smudge, EEAA, MDMarra, voretaq7 Jan 30 '12 at 21:13

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Have you benchmarked your campaign page with ab, siege, jmeter or similar benchmarking software? Shoot the site with the benchmarking software of your choice, see how fast it is / how badly it kills your server.

The numbers themselves are not that high, so unless your campaign site is a resource hog, there shouldn't be problems.

share|improve this answer
Is there any online service instead? I know, but they are using same IP to make all requests, which doesn't make it an accurate test. I've seen but their pricing is ridiculous. – Gajus Jan 25 '12 at 11:55
Why not ? The source IP is largely irrelevant. The requests are all that matter. – adaptr Jan 25 '12 at 11:57
What's wrong with a good old smoke test ab etc. can provide to you? They WILL tell you if your site going down or going to survive your big day. – Janne Pikkarainen Jan 25 '12 at 12:05

A FastEthernet interface will have problems handling large numbers of connections.

If these requests are spread evenly over a 24-hour period, you are predicting on the order of 230 requests per second; this is not a huge amount, but it depends entirely on how long these requests take to process, and the size of the response.

  • What is the mix of dynamic/static content for these requests ?
  • Is the database accessed sanely, i.e. using persistent proxied connections?
  • Is the database schema designed by a DBA, or an amateur ?

Do some local benchmarks using a web stress utility to figure out the answers to the above, and you will be able to better estimate the load this system can handle.

share|improve this answer

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