Live data from Hacker News

Battle-ready Nginx – an optimization guide

blog.zachorr.com

41–46 of 46 posts

Re: Battle-ready Nginx – an optimization guide

#41
post #19

Also useful for nginx: adding the pagespeed module https://github.com/pagespeed/ngx_pagespeed "ngx_pagespeed speeds up your site and reduces page load time by automatically applying web performance best practices to pages and associated assets (CSS, JavaScript, images) without requiring you to modify your existing content or workflow."

pagespeed is impressively helpful, great news when nginx support was announced (a tipping point for me), just wish I knew going in that I had to compile for SPDY instead of using apt

Re: Battle-ready Nginx – an optimization guide

#42

I wish I could find a guide like this for Apache as well. Computing max clients and other options seems like pure guess work and constant failure =/

https://github.com/h5bp/server-configs-apache

This isn't really 1-to-1 with the article. I meant something like max_clients, max_requests_per_child, etc.

The best I know if is my co-workers' efforts here: > https://github.com/genesis/wordpress/pull/64

Re: Battle-ready Nginx – an optimization guide

#43
I would love to see optimization guides with actual benchmarking.

It's like saying `for(var i=..` is faster than `.forEach` without given any numbers.

Always test for performance, do not blindy follow guides or copy paste configuration files in your web server.

Re: Battle-ready Nginx – an optimization guide

#45
post #7

For anyone who is interested in nginx tuning, please follow the H5BP nginx repo: https://github.com/h5bp/server-configs-nginx , which is very well documented already and still being maintained.

Could line 21 of nginx.conf actually be any more arrogant or presumptuous?
Post reply on HN