Disabling mod_gzip: Are there any major disadvantages?

Every month or two, mod_gzip causes me problems by filling up the /tmp partition, which is 1GB on my server, with large .wrk files. This seems to happen all of a sudden so a cron that regularly deletes these files doesn't help. I think that this is related to certain scripts I run that access large (1GB) MySQL tables, though I'm not certain.

So what I'm wondering is: Would there be any real disadvantages or problems caused by me turning mod_gzip off (other than causing minor slowdowns due to lack of caching)? Also, is turning mod_gzip off as simple as changing "mod_gzip_on yes" to "mod_gzip_on no"?

Or instead of turning mod_gzip off, would it be preferable to fiddle with some settings?

Here's the mod_gzip module section in my httpd.conf, if that's necessary:
Code: 
<IfModule mod_gzip.c>
mod_gzip_on yes

mod_gzip_send_vary yes

mod_gzip_dechunk yes
mod_gzip_keep_workfiles No
mod_gzip_temp_dir /tmp
mod_gzip_minimum_file_size  1002
mod_gzip_maximum_file_size  0
mod_gzip_maximum_inmem_size 1000000

mod_gzip_item_include file "\.htm$"
mod_gzip_item_include file "\.html$"
mod_gzip_item_include mime "text/.*"
mod_gzip_item_include file "\.php$"
mod_gzip_item_include mime "jserv-servlet"
mod_gzip_item_include handler "jserv-servlet"
mod_gzip_item_include mime "application/x-httpd-php.*"
mod_gzip_item_include mime "httpd/unix-directory"

mod_gzip_item_exclude file "\.css$"
mod_gzip_item_exclude file "\.js$"
mod_gzip_item_exclude file "\.wml$"
</IfModule>

 

 

 

 

Top