Open
Conversation
The cache command will now create zstd-compressed archives. When decompressing, it attempts to compress as Zstd first, but if the magic bytes do not match, it falls back to gzip compression.
Author
|
Note that the Go |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update the
cachecommand to create Zstd-compressed archives rather than gzip-compressed. In testing, this reduces archive size by 20%, with proportional gains in download times, as well as a 50% reduction in decompression time.This change is backwards-compatible and can handle existing, gzip-compressed archives without changes. To do this, we attempt to see if the file is valid Zstd. For the shell-out archiver, I opted to let
tar's built-in autodetection handle the differentiation. This works on all tested systems.Tested manually on Semaphore Linux- and MacOS cloud runners. Timing improvements measured on our own hardware as Semaphore runners appear to be I/O bound.
Fixes #523. In the future, you might want to delete the old gzip implementation as it's messy.