disable cache compression (#53427)
### What? Disables webpacks cache compression ### Why? CI already compresses the cache. No need for next.js to do that. In fact this actually causes worse experience in multiple ways: * CI compresses the cache after the build has finished. So compressing inline slows down the build. * gzip compression runs with BEST_SPEED optimization, which creates larger cache files. This leads to running into potential cache size limits easier. * Two layers for compression are not efficient in size and speed. Trade-off: * The whole cache will be decompressed on every build, which is less efficient. In a few tests the benefits are greater than the trade offs.
Showing
Please
register
or
sign in
to comment