Use ReleaseFast for ARM64 release archives - #421
Merged
Conversation
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
1 participant
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.
Summary
ReleaseFastinstead ofReleaseSmallstrip=truebehavior unchangedWhy
The prior ARM64 settings were an OOM workaround for LLVM debug-information pressure. Stripping release artifacts removes that amplification, and antflydb/colony#420 moves ARM64 publishing to a dedicated 24 GiB C4A runner rather than the shared pool.
Validation
ReleaseFast+ strip diagnostic build passed in 10m15s with 7,804.95 MiB peak RSS at 12 jobsbuild_zig_release_archive.shpackaging path passed with natural parallelismColony runner change: antflydb/colony#420