agner
Sent: 06 November 2019 09:53
To: David Baker ; slurm-users@lists.schedmd.com
; juergen.s...@uni-ulm.de
Subject: Re: [slurm-users] Running job using our serial queue
Hi David,
if I remember right (we have disabled swap for years now), swapping out
processes seem to slow down the system ov
half
of Marcus Wagner
*Sent:* 05 November 2019 07:47
*To:* slurm-users@lists.schedmd.com
*Subject:* Re: [slurm-users] Running job using our serial queue
Hi David,
doing it the way you do it, is the same way, we do it.
When the Matlab job asks for one CPU, it only gets on CPU this way.
That mean
To: slurm-users@lists.schedmd.com
Subject: Re: [slurm-users] Running job using our serial queue
Hi David,
doing it the way you do it, is the same way, we do it.
When the Matlab job asks for one CPU, it only gets on CPU this way. That means,
that all the processes are bound to this one CPU. So (theoreti
Hi David,
doing it the way you do it, is the same way, we do it.
When the Matlab job asks for one CPU, it only gets on CPU this way. That
means, that all the processes are bound to this one CPU. So
(theoretically) the user is just disturbing himself, if he uses more.
But especially Matlab, t
* David Baker [191104 15:14]:
> It looks like the downside of the serial queue is that jobs from
> different users can interact quite badly.
Hi David,
what exactly do you mean with "jobs from different users can interact
quite badly"?
> [...] On the other hand I wonder if our cgroups setup i
Hello,
We decided to route all jobs requesting from 1 to 20 cores to our serial queue.
Furthermore, the nodes controlled by the serial queue are shared by multiple
users. We did this to try to reduce the level of fragmentation across the
cluster -- our default "batch" queue provides exclusive a
