Lighttpd vs nginx

Lighttpd vs nginx – WikiVS.

Nginx and Lighttpd are probably the two best-known asynchronous servers and Apache is undoubtedly the best known process-based server. […] The main advantage of the asynchronous approach is scalability. In a process-based server, each simultaneous connection requires a thread which incurs significant overhead. An asynchronous server, on the other hand, is event-driven and handles requests in a single (or at least, very few) threads. […] Pulling numbers from thin air for illustrative purposes, serving 10,000 simultaneous connections would probably only cause Nginx to use a few megabytes of RAM whereas Apache would probably consume hundreds of megabytes (if it could do it at all).

Lighttpd runs as a single process with a single thread and non-blocking I/O.

nginx works as one master process but delegates its work unto worker processes.

Nginx is noted to be a good server for sites that need fast, efficient reverse proxies or fast, efficient serving of static content.

Both servers performed extremely well, though it seems that Lighttpd might perform best in a more fragmented file system (smaller files). […] Considering that each would easily saturate the pipeline I doubt a real-world performance difference would be seen.

Lighttpd has support for CGI, FastCGI and SCGI via modules.
Nginx has native module support for FastCGI, SCGI, and uWSGI, and has support for WSGI via a 3rd Party module.


This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s