> On Nov 9, 2018, at 3:14 AM, Bjørn-Helge Mevik wrote:
>
> Noam Bernstein writes:
>
>> Can anyone shed some light on where the _virtual_ memory limit comes from?
>
> Perhaps it comes from a VSizeFactor setting in slurm.conf:
>
> VSizeFactor
> Memory specifications in job re
On Friday, 9 November 2018 2:16:48 PM AEDT Noam Bernstein wrote:
> Can anyone shed some light on where the _virtual_ memory limit comes from?
>
> We're getting jobs killed with the message
> slurmstepd: error: Step 3664.0 exceeded virtual memory limit (79348101120 >
> 72638634393), being killed
Noam Bernstein writes:
> Can anyone shed some light on where the _virtual_ memory limit comes from?
Perhaps it comes from a VSizeFactor setting in slurm.conf:
VSizeFactor
Memory specifications in job requests apply to real memory size
(also known as
resident
Can anyone shed some light on where the _virtual_ memory limit comes from?
We're getting jobs killed with the message
slurmstepd: error: Step 3664.0 exceeded virtual memory limit (79348101120 >
72638634393), being killed
Is this a limit that's dictated by cgroup.conf or by some srun option (like
