You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could trade I/O for CPU (or vice versa) by decreasing (or increasing) the compression ratio of the cached artifacts. We could for example let local builds run with a faster compression, while CI builds could spend a bit more time compressing their outputs so that the created artifacts end up being smaller (and faster to download).
This could work with the existing Zlib compression, but it would probably have a higher impact if we introduced Zstandard compression (see #12809).
cc: @gradle/build-cache
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.
We could trade I/O for CPU (or vice versa) by decreasing (or increasing) the compression ratio of the cached artifacts. We could for example let local builds run with a faster compression, while CI builds could spend a bit more time compressing their outputs so that the created artifacts end up being smaller (and faster to download).
This could work with the existing Zlib compression, but it would probably have a higher impact if we introduced Zstandard compression (see #12809).
cc: @gradle/build-cache
The text was updated successfully, but these errors were encountered: