Results 1 to 3 of 3
Hi everyone!
I am planning on implementing HTTP Compression in my site, I have been reading and I see big advantages by "gzipping" content from server so that bandwidth could ...
- 01-15-2009 #1Just Joined!
- Join Date
- Jan 2009
- Posts
- 16
Apache and HTTP Compression
Hi everyone!
I am planning on implementing HTTP Compression in my site, I have been reading and I see big advantages by "gzipping" content from server so that bandwidth could be reduced when reached to client-side.
From what I read, I could add the following pro's:
- Content is compressed when sent from server to client, leveraging bandwidth traffic, reaching in a "faster" way to the user.
And the con's I understand:
- Compression algorithm requires CPU loads
- Compression takes place with text content, not images, etc
What is your opinion about HTTP Compression? Is it a good idea to implement? Are there any other factors and disadvantages to consider in your opinion?
- 01-15-2009 #2
We did try it with some pages that had a lot of data in them and it was quicker when downloading over a slower connection. Over a fast +2.5mb connection it didn't make that much difference.
We did it using the php zlib library and found that turning it up more than 6 or 7 actually slowed things down under load. It pretty much compressed the whole response stream but did also cause problems with downloadable PDF's, it had be specifically turned off.
I wouldn't do it if you are having no real problem, but if you are, try it and see. Just be prepared to experiment with the compression levelsIf we hit that bullseye, the rest of the dominoes will fall like a house of cards. Checkmate! (Zapp Brannigan)
My new blog. It's probably not as good as I think it is.
- 01-15-2009 #3Just Joined!
- Join Date
- Jan 2009
- Posts
- 16


Reply With Quote
