> oversubscribed the first two cores, whether run from SLURM or directly.
>
> I found a work-around, was to use the "--map-by socket" argument to mpirun.
>
> I don't think I ever figured it out -- it was a short-lifetime test cluster
> that I was using to explor
Dear Support,
I'm seeking clarification about the expected behavior of mpirun in Slurm
jobs.
Our setup consists of using Slurm for resource allocation and OpenMPI
mpirun to launch MPI applications. We have found that when two Slurm jobs
have been allocated different cores on the same compute node
