[slurm-users] ulimit in sbatch script
Mahmood Naderan
mahmood.nt at gmail.com
Tue Apr 17 08:38:57 MDT 2018
That parameter is used in slurm.conf. Should I modify that only on the
head node? Or all nodes? Then should I restart slurm processes?
Regards,
Mahmood
On Tue, Apr 17, 2018 at 4:18 PM, Chris Samuel <chris at csamuel.org> wrote:
> On Tuesday, 17 April 2018 7:23:40 PM AEST Mahmood Naderan wrote:
>
>> [hamid at rocks7 case1_source2]$ scontrol show config | fgrep VSizeFactor
>> VSizeFactor = 110 percent
>
> Great, I think that's the cause of the limit you are seeing..
>
> VSizeFactor
> Memory specifications in job requests apply to real memory size
> (also known as resident set size). It is possible to enforce
> virtual memory limits for both jobs and job steps by limiting
> their virtual memory to some percentage of their real memory
> allocation. The VSizeFactor parameter specifies the job's or job
> step's virtual memory limit as a percentage of its real memory
> limit. For example, if a job's real memory limit is 500MB and
> VSizeFactor is set to 101 then the job will be killed if its
> real memory exceeds 500MB or its virtual memory exceeds 505MB
> (101 percent of the real memory limit). The default value is 0,
> which disables enforcement of virtual memory limits. The value
> may not exceed 65533 percent.
>
> Setting it to 0 should make that limit go away.
>
> All the best,
> Chris
> --
> Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
>
>
More information about the slurm-users
mailing list