News for hackers. Stuff that matters.
Re:Google Releases mod_pagespeed for Apache by gawker on Wednesday November 03, 2010 @03:31PM (#1866123)
Would love something like this for nginx - Apache's just using too much memory.
Re:Google Releases mod_pagespeed for Apache by easp on Wednesday November 03, 2010 @09:50PM (#1867274)
Put nginx in front of apache and allow it to buffer responses. That way apache can move on to rendering the next request while nginix empties the buffer. Each apache process still uses just as much memory, but they can get more work done, because they aren't tying up memory while they push the buffered response out.
Re:Google Releases mod_pagespeed for Apache by gawker on Thursday November 04, 2010 @10:52AM (#1869096)
True that. But it's just a wish from my perspective since I'm running on a VPS with limited memory so I can't really afford to have both running.
Re:Google Releases mod_pagespeed for Apache by necro on Wednesday November 03, 2010 @04:15PM (#1866304)
Most of these are micro optimizations that matter most on a larger site. Most large site do not use Apache for static content. I agree, nginx would be a better first choice for a module.

One thing that may not be obvious about minimization is that it does not yield much size reduction when coupled with gzip. You may see 30% decrease in size with minimization on the plain file, but when you gzip both the plain and minimized you may only see a difference for a couple of hundred bytes. If you are worried about speed, you should be using gzip for static content.

Re:Google Releases mod_pagespeed for Apache by 56quarters on Wednesday November 03, 2010 @10:01PM (#1867301)
I've found using minimization to give up 40% smaller files even after gzip. Even so, combining multiple JS or CSS files into single one and using image sprites will probably be your biggest win.
Re:Google Releases mod_pagespeed for Apache by gawker on Thursday November 04, 2010 @10:55AM (#1869109)
I've seen similar results. It's nice to see it everything do it on the fly but I'm guessing doing all these optimizations on a large website will take up more processor cycles?