On Saturday, 22 September 2018 4:19:09 PM AEST Raymond Wan wrote: > SLURM's ability to suspend jobs must be storing the state in a > location outside of this 512 GB. So, you're not helping this by > allocating more swap.
I don't believe that's the case. My understanding is that in this mode it's just sending processes SIGSTOP and then launching the incoming job so you should really have enough swap for the previous job to get swapped out to in order to free up RAM for the incoming job. -- Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
