windows: -j2 + 24G swap for the C++ memory peaks#86
Merged
Conversation
-j3+14G got PAST the Rust wall (10min -> 28min, deep into C++), then stalled 13min on dom/canvas and got SIGTERM'd: swap-death on the heavy WebGL/bindings C++ TUs. Halve concurrent heavy compiles (-j2) and give swap real headroom (24G; runner has 100G+ free disk). Slower but should clear the C++ memory peaks.
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.
The swap+-j3 change worked as intended on Rust — the build went from dying at ~10min to running 28+min deep into C++ DOM compilation. It then stalled 13min on
dom/canvas(heavy WebGL TU) and got SIGTERM'd: swap-death on the memory-heavy C++ translation units. Drop to-j2(fewer concurrent heavy compiles) and grow swap to 24G (runner has 100G+ free). Slower but should clear the C++ peaks the way it cleared the Rust ones.