Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

The ISP hosting a mostly static web site complains when certain users start to hammer the site at around 30 hits/second. The machine slows to a crawl, apparently. The files can be simple pages with a few graphics, to fairly large files. There are other sites hosted on the server, so this is not good news.

Should Apache be able to take this load? Are there tips that the ISP can use to tune the server for this? Is there anything to tweak on the pages themselves?

share|improve this question
add comment

2 Answers

up vote 4 down vote accepted

Wow... 30 static requests per second should be nothing for a well-tuned Apache. There's something going pretty badly wrong there. Either the machine is running at capacity already, or it's mistuned. My three primary tweaks for Apache are:

  • KeepAlive On
  • KeepAliveTimeout 2 (or 15 if you use the worker MPM)
  • ExtendedStatus Off

I've got more general "make your webserver handle more capacity" tips in this wiki article from my work, and there's a lot more "tweaking Apache" tips in this devside article.

Honestly, though, if your ISP isn't already up on these sorts of things, it's time to be finding a new webhost. Customers shouldn't have to go asking serverfault for tips to pass onto their hosting company.

share|improve this answer
add comment

I have found that Apache can handle hundreds to thousands of static request per second without being overloaded. The bandwidth usually gets used up before the server does. Is the CPU maxing out? Are the hard drives thrashing? Is the server running out of memory? Saying a "machine slows to a crawl" could be so many things.

share|improve this answer
add comment

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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