Avoid using pargzip for compression #558
Merged
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.
Switching from pargzip to pgzip showed much better efficiency over in apko, so let's do the same here to see if it frees up any resources during megabuilds.
For smaller sections (control and signature), this just uses klauspost's gzip implementation instead of pgzip since don't need parallel compression for such tiny inputs.
This will change the hashes of APKs because the compression will be different, but I don't believe we rely on reproducibility in melange.