Aspects


vs


Apache

Use this tag (along with an appropriate programming-language tag) for programming questions relating to the Apache HTTP Server

Lighttpd

Lighttpd is a lightweight and high-performance event-driven web server.

Webserver fewer resources

Quality Example
Less ram

"Nginx or lighttpd in fastcgi mode use less ram than apache and they can handle more concurrent connections"

from question "PHP Image Generation"

Less

"It may even use a different server software say nginx or lighttpd that has less overhead than the traditional apache setup"

from question "What are the benefits of storing client-side files (img, css, javascript) in subdomain?"

Fewer resources

"Since you ve switched to lighttpd the webserver itself is going to use fewer resources than apache would but apache is rarely the bottleneck unless you ve run out of ram or seriously misconfigured it"

from question "What are the most likely scaling issues a website with a modified lamp stack (Lighttpd instead of Apache) on EC2 will encounter as it grows?"

Others

Quality Example
Even faster

"For instance in some benchmarks lighttpd is even faster at serving static resources than apache"

from question "File / Image Replication"

More suitable

"This is my first experience setting up lighttpd as i thought it would be more suitable than apache in this case"

from question "Optimise Lighttpd for lots of connections serving small files"

Faster

"- if you move towards more static content or go the fastcgi way lighttpd is faster than apache"

from question "What webserver / mod / technique should I use to serve everything from memory?"

More powerful

"The benefit of both apache is more powerful and extensible useless if you don t need that power but anyway... and lighttpd is faster at static content"

from question "Apache or lighttpd"

Back to Home
Data comes from Stack Exchange with CC-BY-SA-3.0