Disable thread binding #730
Open
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
The resource manager does a much better job at distributing cores than whatever it is we are doing. And running multiple processes per node is not uncommon these days. Signed-off-by: Joseph Schuchart <[email protected]>
bosilca
approved these changes
Feb 17, 2025
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.
The resource manager does a much better job at distributing cores than whatever it is we are doing. And running multiple processes per node is not uncommon these days.
#515 is two years and it seems to be an intractable problem. @therault has at least one recent example where the forced binding to the same cores became a footgun for PaRSEC. We can re-enable the binding once someone comes up with a solution but until then we should play nice.