4 ms·
I've used Lighttpd, Cherokee, Nginx and of course Apache (although stripped down for speed) on a high load production site for serving static files and reverse
by zepolen 18y ago
I've used Lighttpd, Cherokee, Nginx and of course Apache (although stripped down for speed) on a high load production site for serving static files and reverse proxying.
Nginx wins no contest. Highly stable, serving for almost 2 years now with zero issues.
Lots of features, much simpler config, uses less resources.
Hot config reloading. Hot binary upgrading.
Low grade? Hardly.
Issues with others:
Lighttpd - configing slightly annoying, uses more cpu and memory
Apache - slow performance and memory hog even when stripped of all it's extra modules, (just try and support 5000 keep alive connections on it)
Cherokee - very nice, well thought out and featureful and fast but had some stability problems in production, I may take a look at it again later on because it has a sweet admin interface
- zeeone 18y agoMany thanks for all answers so far! I talked to a Ukrainian programmer and a friend of mine, who said he knew the guy who programmed nginx. He said that nginx was designed as a load balancer for Apache. I've been reading its docs for two days now and I can't find anything like that, but then again most of the docs are in Russian. Am I missing something? Is nginx a stand alone server or an addition to Apache?
- moonpolysoft 18y agoIt's standalone. Nginx really shines as a reverse proxy, but it has an fcgi module that can be used to do that as well.
- anotherjesse 18y agoEnglish Docs are here: http://wiki.nginx.org/Main http://wiki.nginx.org/Main - the site used to be wiki.codemongers.com but it is now under nginx.org