[slurm-users] Slurm does not set memory.limit_in_bytes for tasks (but does for steps)

Hello everyone, I came across a weird behavior and was wondering if this is a bug, oversight, or intended? It appears that Slurm does not set memory.limit_in_bytes at the task level, but it does set it at the step level and above. Observe: $ grep memory /proc/$$/cgroup 10:memory:/slurm/uid_2001/

Re: [slurm-users] [External] incorrect number of cpu's being reported in srun job

Yes, You need to use the cgroups plugin. On Fri, Jun 18, 2021, 12:29 AM Sid Young wrote: > G'Day all, > > I've had a question from a user of our new HPC, the following should > explain it: > > ➜ srun -N 1 --cpus-per-task 8 --time 01:00:00 --mem 2g --pty python3 > Python 3.6.8 (default, Nov 16

Re: [slurm-users] [External] incorrect number of cpu's being reported in srun job

Thanks for the reply... I will look into how to configure it. Sid Young Translational Research Institute On Wed, Jun 23, 2021 at 7:06 AM Prentice Bisbal wrote: > Yes, > > You need to use the cgroups plugin. > > > On Fri, Jun 18, 2021, 12:29 AM Sid Young wrote: > >> G'Day all, >> >> I've had a