Fix ARM64 builds: increase JVM heap and apply memory optimizations#6755
Merged
Conversation
Automation reverts envoy.bazelrc back to 3GB when syncing from upstream. Add override in .bazelrc (which imports after envoy.bazelrc) to permanently set heap to 4GB for ARM64 builds. The 3GB limit causes memory pressure during large downloads which breaks gRPC remote cache connections.
istio-testing
added
the
size/XS
PetrMc
added
cherrypick/master
keithmattix
approved these changes
Jan 12, 2026
Collaborator
|
In response to a cherrypick label: new pull request created: #6756 |
This was referenced Jan 12, 2026
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
3 participants
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.
Fixes ARM64 build failures by increasing JVM heap from 3GB to 4GB and applying Bazel memory optimization flags to all remote cache builds. The CI uses --remote_cache but not --config=remote-ci, so the optimization flags weren't being applied. This applies both fixes that were in #6726. Fixes #6752