perf(mpi): cap thread pools for MPI and document policy - #76
Merged
lmoresi merged 2 commits intoMar 10, 2026
Merged
Conversation
Apply MPI-safe default thread caps in the uw launcher and add a runtime oversubscription warning/policy in underworld3 import logic; document behavior and override controls in parallel-computing docs. Underworld development team with AI support from Claude Code
Contributor
Author
|
With this fix and OpenMPI on macOS, I am no longer seeing any CPU spikes (>100%). |
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
2 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.
Cherry-picks only these commits from gthyagi:feature/boundary-integrals:\n- 014e97c perf(mpi): cap thread pools for MPI and document policy\n- d42f6b2 revert: restore uw wrapper from development\n\nThis keeps boundary-integral development/testing isolated in the original branch/PR.