Hi folks,
After an extended hiatus (I forgot to resubscribe after going away for a
few weeks) I'm back.. ;-)
We are using QOS's for projects which have been granted a fixed set of
time for higher priority work which works nicely, but have just been
asked the obvious question "how much time do we
I don't really have enough experience with QoS's to give a slicker
method but you could use squeue --qos to poll the QoS and then write a
wrapper to do the summarization. It's hacky but it should work.
-Paul Edmon-
On 8/19/2018 9:26 PM, Christopher Samuel wrote:
Hi folks,
After an extended
Hi Paul,
On 20/08/18 11:36, Paul Edmon wrote:
I don't really have enough experience with QoS's to give a slicker
method but you could use squeue --qos to poll the QoS and then write a
wrapper to do the summarization. It's hacky but it should work.
I was thinking sacct -q ${QOS} to pull info
That variable does not exist somehow on my environment. Is it possible
my Slurm version (17.02.3) does not include it?
Thanks
On 17/08/18 11:04, Bjørn-Helge Mevik wrote:
Yes. It is documented in sbatch(1):
SLURM_MEM_PER_CPU
Same as --mem-per-cpu
SLURM_MEM_PER_N
