You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When launching multiple executions using prun the CPU binds overlap.
shell$ prun -np 1 --map-by node:pe=4 ./a.out
Would be placed on cores [0-3].
If another process is launched with the same settings (while the first one is still running) it will be placed on cores [1-4]. Instead of some non-overlapping range. Otherwise the affinity mapping works perfectly.
process on node1 with cores Cpus_allowed_list: 0-3,128-131
process on node1 with cores Cpus_allowed_list: 1-4,129-132
Is this expected behavior or am I perhaps missing some option or configuration to make the placement non-overlapping ? Based on the --display map-devel output multiple cpus/proc does not seem to affect the number of slots used.
Same behavior is observed when running locally and using slurm (21.08) integration (prrte started within a job allocation and srun starts prte on each node).
The text was updated successfully, but these errors were encountered:
Background information
Simultaneous executions requesting multiple cores overlap.
Wondering if this is expected or a bug.
Please describe the system on which you are running
RHEL 7.9
AMD EPYC 7402 (dual socket)
InfiniBand HDR200
Details of the problem
When launching multiple executions using
prun
the CPU binds overlap.Would be placed on cores [0-3].
If another process is launched with the same settings (while the first one is still running) it will be placed on cores [1-4]. Instead of some non-overlapping range. Otherwise the affinity mapping works perfectly.
Full:
->
Is this expected behavior or am I perhaps missing some option or configuration to make the placement non-overlapping ? Based on the
--display map-devel
output multiple cpus/proc does not seem to affect the number of slots used.Same behavior is observed when running locally and using slurm (21.08) integration (prrte started within a job allocation and srun starts prte on each node).
The text was updated successfully, but these errors were encountered: