Use FI_MR_CACHE_MONITOR=kdreg2 for all nersc machines
#6687
+5
−0
Conversation
This file contains 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
ndkeen
added
Machine Files
BFB
|
|
I'm now seeing it looks like this will fix #6516, which would be great as it will allow me to update the GCC compiler version. Confirmed that using |
ambrad
approved these changes
Oct 19, 2024
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.
With new slighshot software (s2.2 h11.0.1), I encountered some hangs in our init for certain cases at higher node counts.
Using
FI_MR_CACHE_MONITOR=kdreg2avoids any issues.HPE claims this might be default one day.
For one HR F-case at 256 nodes, using
kdreg2was about 1% slower.Fixes #6655
I also found some other issues (some with lower node-count) that this fixes (even on pm-cpu currently):
Fixes #6516
Fixes #6451
Fixes #6521
[bfb]