Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


gzip_comp_level
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

gzip_comp_level

NoxterNoxter Member
edited December 2012 in General

Just curious what value some of you folks use? Although my machines have plenty of processing power, 6 seems a bit more sluggish than for example 1. Which doesn't make sense... if content is getting compressed, shouldn't the end user benefit in faster load times? We're talking marginal compression from 1 to 6, so... it must be in my head.

The server's load is very stable (spikes due to backups):
http://i.imgur.com/Ui1q5.png

What config do most of you folks use?

Comments

  • Gzip compression for HTTP traffic or what?

    For HTTP stuff I leave as defaults, which typically are on the very low end side. Gains with the added compression are minimal and chews up CPU time and delays delivery of content. Plus users already taxed CPU has additional work to decompress.

  • Regarding http compression:
    I have tested compression rates on many web servers, and it seems the more compression you turn on, the slower it will get for the end user. I agree that using default compression levels for most web servers should be best practice, unless you have a particular need, then I would say to test compression along with an http benchmark tool to get the best results for your site.

  • I enabled compression and got my website from like 3MB of data down to 400KB

  • For heavy JavaScript / CSS etc it works great. For small HTML pages maybe not.

  • I always use level 1. More than that I think it's just burning additional CPU for very little benefit.

Sign In or Register to comment.