so MaxRSS is a good estimate of how much RAM is needed to run a
> given job.
>
>
>
> Gareth
>
>
>
> *From:* slurm-users [mailto:slurm-users-boun...@lists.schedmd.com] *On
> Behalf Of *E.S. Rosenberg
> *Sent:* Tuesday, 17 April 2018 10:42 PM
> *To:* Slurm User Community
good estimate of how much RAM is needed to run a given job.
Gareth
From: slurm-users [mailto:slurm-users-boun...@lists.schedmd.com] On Behalf Of
E.S. Rosenberg
Sent: Tuesday, 17 April 2018 10:42 PM
To: Slurm User Community List
Subject: Re: [slurm-users] Way MaxRSS should be interpreted
Hi
Hi Loris,
Thanks for your explanation!
I would have interpreted as max(sum()).
Is there a way to get max(sum()) or at least sum form of sum()? The
assumption that all processes are peaking at the same value is not a valid
one unless all threads have essentially the same workload...
Thanks again!
E
Hi Eli,
"E.S. Rosenberg" writes:
> Hi fellow slurm users,
> We have been struggling for a while with understanding how MaxRSS is reported.
>
> This because jobs often die with MaxRSS not even approaching 10% of the
> requested memory sometimes.
>
> I just found the following document:
> https:/
Hi fellow slurm users,
We have been struggling for a while with understanding how MaxRSS is
reported.
This because jobs often die with MaxRSS not even approaching 10% of the
requested memory sometimes.
I just found the following document:
https://research.csc.fi/-/a
It says:
"*maxrss *= maximum
