The .htaccess file shipped by Drupal already enabled gziping of pages if the client supports it.
As per the thread in the performance group, for most use cases it is more performant to remove this variable and associated behaviour. Apache is optimised to handle the compression transparently depending on the client. Although this will result in larger amounts of data being stored in the page cache, there isn't the overhead of compression (and in some cases uncompressing) the cached pages.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | drupal-1321918-remove-page-compression.patch | 14.27 KB | skwashd |
Comments
Comment #1
skwashd commentedAnd here is the patch for it.
Comment #2
dalinSure doing it at the Apache level is more performant. But what about sites that don't have access to that (i.e. shared hosting). Will this patch not decrease performance for those sites?
Comment #3
damien tournoud commentedIt should be more efficient to handle that in Drupal. More clients those days support compression, so it's better to store the compressed data directly in the cache and serve it transparently. On-the-fly compression at the Apache level doesn't seem like a good idea.
Comment #4
damien tournoud commentedThat's not actually true, as far as I know.
Comment #5
thedavidmeister commented#1: drupal-1321918-remove-page-compression.patch queued for re-testing.
Comment #7
damien tournoud commentedThe same thread has since proven that this is not a good idea.