2 ms·
There really is no such thing as a sane default for compression in general. There are three common use cases and each one demands different tradeoffs. Maximum c
by klodolph 8y ago
There really is no such thing as a sane default for compression in general. There are three common use cases and each one demands different tradeoffs. Maximum compression is often suitable for compression once and decompression many times. Lower compression is useful for compression/decompression once. A middle value is useful for compression once/decompression less than once. Then you choose different values based on the relative costs of CPU, memory, network bandwidth, disk space, etc.
“Maximum” is good because it handles a common use case. When you’re running a CLI tool, you’re much more likely to be processing static assets which are served many times. So “maximum” is a good guess of what the user wants.