What should I know about managing IIS 6.0s compression Cache Settings in Advanced Settings?
When you compress a file, there is minor processing penalty. Like all good compression solutions, IIS 6.0 is designed with a cache for compressed content. The first time a file that is eligible for compression is requested by a browser, the page is served uncompressed, and then the internal IIS 6.0 compression engine places the file in a queue for compression. Once compressed, a copy of the compressed file is stored in the compression cache, and the next time the file is requested, it is served from the cache compressed (as long as the resource has not been modified in the meantime). By selecting Settings > Global > Advanced Settings and then the Cache Settings tab, ZipEnable provides administration over the location that IIS 6.0 stores it’s compression cache, the size of the compression cache, and the number of files to delete from the cache once it reaches maximum set limits (limiting cache size is not recommended, as it can incur extra processing time).
