More Need For More Speed: Compressed Cache Files

[serpent_driver]

LiteSpeed compresses chache files. This seems to be good to reduce the need for disk space, but cache files need to be decompressed to answer a request. To me, this takes too time and causes a higher load for decompressing. Especially shared hostings with lower power are affected from this, so the question is can the compression be disabled?

If not, what is the advantage of compressed cached files if they must be decompressed before a request can be answered and if data are compressed again by gzip/brotli?

If yes, how can compression of cached files be disabled?

Happy New Year

 

[mistwang]

Happy New year!

Most browser clients support compression, most time, compressed data are served as is to the client. server wont do decompress and compress again if it can be avoided.

LiteSpeed can store both BROTLI compressed and GZIP compressed copy in cache, it usually takes less disk space than uncompressed copy.

LiteSpeed is capable of serving GZIP compressed ESI page, only need to compress the dynamic holes, the main page do not need to be decompressed and compressed again.

Decompress is much faster than compress.

There is no advantage store cached compressible page without compression to me.

 

[serpent_driver]

Okay, the way you describe it makes sense.

Thank you!