On a side note, I have a minor documentation bug report:
On this page http://slurm.schedmd.com/cpu_management.html there is a link
to
-s, --oversubscribe
which points to
http://slurm.schedmd.com/srun.html#OPT_share
The actual link is
http://slurm.schedmd.com/srun.html#OPT_oversubscribe
Our nodes have
Sockets=2 CoresPerSocket=10 ThreadsPerCore=2
CPUs are set to 40 and SelectTypeParameters=CR_CPU
According to this FAQ, this is "not a typical configuration".
http://slurm.schedmd.com/faq.html#cpu_count
Which is fine, I am aware that this is the set up - I did the configuration.
Hi Janne,
> AFAIU the major optimization wrt. array job scheduling is that if the
> scheduler finds that it cannot schedule a job in a job array, it skips over
> all the rest of the jobs in the array.
If that’s true, then I think most of my worries should be nullified. That
would definitely
On 21/09/16 14:15, Christopher benjamin Coffey wrote:
> I’d like to get some feedback on this please from other sites and the
> developers if possible. Thank you!
The best I can offer is this from the job array documentation from Slurm:
# When a job array is submitted to Slurm, only one job
Hi,
AFAIU the major optimization wrt. array job scheduling is that if the scheduler
finds that it cannot schedule a job in a job array, it skips over all the rest
of the jobs in the array. There's also some memory benefits, e.g. a pending job
array is stored as a single object in the job
