4 ms·
Would love something like this for nginx - Apache's just using too much memory.
by gawker 16y ago
Would love something like this for nginx - Apache's just using too much memory.
- necro 16y agoMost 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.
- 56quarters 16y agoI'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.
- gawker 16y agoI'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?
- easp 16y agoPut 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.
- gawker 16y agoTrue 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.