3 ms·
I'd guess anywhere from 100GB to 1TB every month depending on whether you did the inline style suggestion and/or the gzip suggestion. This page gzip'd: http://
by gduffy 16y ago
I'd guess anywhere from 100GB to 1TB every month depending on whether you did the inline style suggestion and/or the gzip suggestion.
This page gzip'd: http://www.google.com/search?q=30+*+1e6+*+(52KB-10KB) http://www.google.com/search?q=30+*+1e6+*+(52KB-10KB)
Front page gzip'd: http://www.google.com/search?q=30+*+1e6+*+(25KB-5KB) http://www.google.com/search?q=30+*+1e6+*+(25KB-5KB)
So probably not worth it :)
- zepolen 16y agoGzip is always worth it, it lowers the per client transmission time and because browsers render gzipped pages after they have been loaded the page appears instantly in one go. It actually creates the impression of a faster site even if the real time to load is the same. Considering the only thing necessary to enable gzip is to enable it in the front facing web server and that it uses barely any cpu at all on level 4 I don't see why anyone wouldn't use it.
- pg 16y agothe only thing necessary to enable gzip is to enable it in the front facing web server Somewhat more is necessary in this case.
- deleted 16y ago[deleted]
- wladimir 16y agoGiven that gzipping is generally a matter of adding a line to the web server configuration file, and it gives so much savings, I'd say it's worth it. As for the HTML suggestion, I'd skip that one, it's just a few bytes per comment and needs actual code changes.