Repository navigation
Conversation
The libxc 7.0.0 build for x86_64/amd/zen4 in EESSI/software-layer#1772 was killed twice with the same OOM in cc1 at half the cores. A divider of 3 gives 5 jobs on a 16-core build node instead of 8.
Contributor
|
Testing this in EESSI/software-layer#1772 (comment) |
Contributor
|
Still went OOM - or so it seems. We can try to reduce parallelism even further. But by now I'm not convinced that it isn't the memory consumption of one of the threads that is a bottleneck... The good news I guess is that the build time wasn't all that different. Maybe we should just really crank it, go for a reduction of 8 (i.e. 2 cores), see if that works. It'll take the least amount of human time to just try this. |
HaoZeke
changed the title
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.
Companion to EESSI/software-layer#1772.
The libxc 7.0.0 build for x86_64/amd/zen4 there was killed twice by the out-of-memory killer in cc1.
This caps the libxc build at 8 parallel jobs on every target, instead of dividing the core count by 3, so a large build node no longer starts more cc1 processes than its memory can hold.
The A64FX limit stays at 6.
AI disclosure: an AI coding assistant helped write this change.
I reviewed it and checked the builds and tests myself.