Re: [slurm-users] Question about sbatch options: -n, and --cpus-per-task

2022-03-24 Thread Ralph Castain
Well, there is indeed a difference - and it is significant. > On Mar 24, 2022, at 12:32 PM, David Henkemeyer > wrote: > > Assuming -N is 1 (meaning, this job needs only one node), then is there a > difference between any of these 3 flag combinations: > > -n 64 (leaving cpus-per-task to be the

Re: [slurm-users] Reserving slots with sbatch and OpenMpi

2022-03-14 Thread Ralph Castain
; Yes, sorry. It is > > mpirun -wdir "." ./parent > > I expected mpirun to pick up the job parameters from the SLURM_* environment > variables created by sbatch. > > Thanks, > Kurt > > From: slurm-users On Behalf Of Ralph > Castain > Sent:

Re: [slurm-users] Reserving slots with sbatch and OpenMpi

2022-03-11 Thread Ralph Castain
I assume you are running the job via mpirun? Can you share the mpirun cmd line? > On Mar 11, 2022, at 11:31 AM, Mccall, Kurt E. (MSFC-EV41) > wrote: > > With sbatch, what is the proper way to launch 5 tasks each on a single node, > but reserve two slots on each node so that the original tasks

[slurm-users] Slurm-PMIx integration

2022-03-02 Thread Ralph Castain
Current Slurm official repository branches contain only a limited PMIx integration, primarily constrained to providing support for the traditional put-get exchange of key-value pairs. The support is also restricted to PMIx v3.x releases and below, though this restriction is due to a configure l