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

could you pelase tell me what's the difference (i never heard of lighttpd before) ? pro / cons ?

and what would you pick for a website who have to deal with a lot of querys (like 20,000 min per day) ?


share|improve this question
up vote 2 down vote accepted

It really depends what you want to do and what resources you have. But unless you have a very heavy traffic (which you do not have, 20k/day is fairly light) or very complex/dynamic pages that require a lot of server processing, just pick a server with the required features. Apache is a safe bet, in my opinion, and it is not slow, as it is often implied.

Just as a reference, one web site I manage runs apache on an old dual CPU/2G ram and serves 1+ M files per day w/o breaking a sweat (mostly images -- dynamic pages run on app server).

share|improve this answer
(celeron 2ghz + 2g ddr). Thanks for your time – Tristan Apr 28 '10 at 18:37
Also, if you have dynamic pages with a database, chances are that that will be your bottleneck, not the web server. – Dan Andreatta Apr 28 '10 at 18:47

As long as you don't need any plugins which are only available for apache, lighttpd is usually a better choice when performance is an issue.

share|improve this answer
Ah :D so i've one for apache , and another for lighttpd :p – Tristan Apr 28 '10 at 18:38

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.