Live data from Hacker News

Nginx vs. Apache in AWS

blog.celingest.com

41–44 of 44 posts

Re: Nginx vs. Apache in AWS

#41

Earlier quoted context omitted.

Hell, it would have been great if they had used a real closed testbed on a local network instead of AWS. That would give you reproducible test results that aren't influenced by things like communal server resources and a communal network. Regardless, they put zero thought into what makes each application work to its peak performance and just picked two random configurations, probably based on defaults that we know to…

Call me stupid. But maybe Apache shouldn't ship defaults that have poor performance ?

Well stupid, Apache ships with the default settings it does for historical expectations of its users. But the application's tuning is driven largely by how you use it, as there are several workers for Apache that all are useful in different situations and require vastly different configuration options. This is to say nothing of the kernel options which also need to be tuned to the application.

The defaults are just defaults. They need to be changed to improve performance.

Re: Nginx vs. Apache in AWS

#42
post #3

Lighttpd is missing... but good benchmark anyway.

I actually really like the lighttpd config structure, but its not actively maintained and doesn't have the amazing community that nginx has. It is clear that nginx has won the high performance web-server battle..

The sensible config syntax is the reason I still use lighttpd. http://wiki.nginx.org/IfIsEvil

Re: Nginx vs. Apache in AWS

#43

Earlier quoted context omitted.

Optimized for what? For which circumstances? What software fits all?

Optimized for serving HTTP requests at a high throughput. What possible reason is there for Apache deliberately slowing that down ?

Are you serious?

Just off the top of my head, how about...

- Simplifying the initial setup?

- Making the default configuration simpler to understand?

- Dialing up logging to make your initial configuration easier to monitor / debug?

- Performance options with security implications (e.g. ok if other parts of your infrastructure are up-to-snuff, but otherwise...)?

The default configuration should be tuned to the needs of whoever is most likely to be using it. I have a hunch that's far more likely to be people using an Apache server (maybe even a web server) for the first time than people with extreme performance requirements.

Re: Nginx vs. Apache in AWS

#44

Disclaimer: I work at AWS, I'm not speaking for my employer. I also helped write Apache httpd, and I'm not speaking for Apache either. Just on my own behalf. The Apache configuration in the benchmark isn't great, using values of; MaxClients 400 MinSpareThreads 25 MaxSpareThreads 75 ThreadsPerChild 25 means that Apache will be doing extra work to spin up and spin down threads in response to the load. It's best to keep…

"Apache is awesome, but I run nginx on my own EC2 micro instance. It's less hassle."

...enough said!

Post reply on HN