Re: [slurm-users] srun and --cpus-per-task

2022-03-25 Thread Durai Arasan
Hello all, Thanks for the useful observations. Here is some further env vars: # non problematic case $ srun -c 3 --partition=gpu-2080ti env SRUN_DEBUG=3 SLURM_JOB_CPUS_PER_NODE=4 SLURM_NTASKS=1 SLURM_NPROCS=1 SLURM_CPUS_PER_TASK=3 SLURM_STEP_ID=0 SLURM_STEPID=0 SLURM_NNODES=1

Re: [slurm-users] srun and --cpus-per-task

2022-03-25 Thread Juergen Salk
Hi Bjørn-Helge, that's very similar to what we did as well in order to avoid confusion with Core vs. Threads vs. CPU counts when Hyperthreading is kept enabled in the BIOS. Adding CPUs= (not ) will tell Slurm to only schedule physical cores. We have SelectType=select/cons_res

Re: [slurm-users] srun and --cpus-per-task

2022-03-25 Thread Bjørn-Helge Mevik
Hermann Schwärzler writes: > Do you happen to know if there is a difference between setting CPUs > explicitely like you do it and not setting it but using > "ThreadsPerCore=1"? > > My guess is that there is no difference and in both cases only the > physical cores are "handed out to jobs". But

Re: [slurm-users] srun and --cpus-per-task

2022-03-25 Thread Hermann Schwärzler
Hi Bjørn-Helge, hi everone, ok, I see. I also just re-read the documentation to find this in the description of the "CPUs" option: "This can be useful when you want to schedule only the cores on a hyper-threaded node. If CPUs is omitted, its default will be set equal to the product of

[slurm-users] user_name attribute missing in job response from slurm rest api method jobs

2022-03-25 Thread Filip Holka
Hallo, Let me explain a problem I have with one of the methods from slurmrest api, namley the “jobs” method. When I issue the call: curl -H "X-SLURM-USER-NAME:holka" -H "X-SLURM-USER-TOKEN:${SLURM_JWT}" http://172.20.102.31:6820/slurm/v0.0.37/jobs

Re: [slurm-users] Disable exclusive flag for users

2022-03-25 Thread Pankaj Dorlikar
thanks -Original Message- From: slurm-users On Behalf Of Ward Poelmans Sent: 25 March 2022 13:10 To: slurm-users@lists.schedmd.com Subject: Re: [slurm-users] Disable exclusive flag for users Hi PVD, On 25/03/2022 01:55, pankajd wrote: > We have slurm 21.08.6 and GPUs in our compute

Re: [slurm-users] Disable exclusive flag for users

2022-03-25 Thread Bjørn-Helge Mevik
pankajd writes: > We have slurm 21.08.6 and GPUs in our compute nodes. We want to restrict / > disable the use of "exclusive" flag in srun for users. How should we do it? Two options would be to use the CLI_filter plugin or the job_submit plugin. If you want the enforcement to be guaranteed,

Re: [slurm-users] srun and --cpus-per-task

2022-03-25 Thread Bjørn-Helge Mevik
For what it's worth, we have a similar setup, with one crucial difference: we are handing out physical cores to jobs, not hyperthreads, and we are *not* seeing this behaviour: $ srun --cpus-per-task=1 -t 10 --mem-per-cpu=1g -A nnk -q devel echo foo srun: job 5371678 queued and waiting for

Re: [slurm-users] Disable exclusive flag for users

2022-03-25 Thread Ward Poelmans
Hi PVD, On 25/03/2022 01:55, pankajd wrote: We have slurm 21.08.6 and GPUs in our compute nodes. We want to restrict / disable the use of "exclusive" flag in srun for users. How should we do it? You can check for the flag in the job_submit.lua plugin and reject it if it's used while also