Small fix in Perlmutter GPU sbatch script #5683
Merged
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.
Changes in Perlmutter GPU job script:
from
#SBATCH --cpus-per-task=16
to#SBATCH --cpus-per-task=32
.This is to request (v)cores in consecutive blocks.
GPU 3 is closest to CPU cores 0-15, 64-79,
GPU 2 to CPU cores 16-31, 80-95,
...
If
--cpus-per-task=16
, MPI ranks 0 and 1 are mapped to cores 0 and 8.If
--cpus-per-task=32
, MPI ranks 0 and 1 are mapped to cores 0 and 16.Visual representation

@ax3l @WeiqunZhang is this correct?