LightHttpd vs Nginx

Question

Well, I have seen this question quite a few times here on SO and in the same way as elsewhere on the Internet. But ... they are all pretty old, so I'll post it again.

I have the following needs:

• Ability to handle many simultaneous HTTP connections (such as comets). It is for this reason that I am looking at other web servers, not apache.

• Should be easy to install and run PHP

• A reverse proxy server is required to forward specific requests to an alternate web server (apache or yaw) to another port.

I know that nginx does not have fast cgi support by default. Although lighthttpd seems to have this, I am reading complaints about memory leaks. Is the memory leak problem still common?

What do you recommend now: nginx or lighthttpd? Or something different? Why?

Answer 1

Both have excellent performance. Using FastCGI with Lighttpd is a bit simpler because it is able to create processes on its own (the disadvantage is that it starts fastcgi servers as the same user as the web server), while nginx requires a bit of manual work . Both of them are perfectly capable of acting as reverse proxies and load balancers.

, nginx front-end Apache. , nginx + apache2 + mod_php - , nginx + php-fastcgi. , .

, IMHO nginx - , .