Quoting tog <[email protected]>:
Dear all
I am using slurm 2.2.0 on ubuntu server 10.04 (LTS).
My machine is having computing nodes containing: 1 socket having 4 cores + HT
My configuration files contains the following definitions:
TaskPlugin=task/affinity
SelectType=select/cons_res
SelectTypeParameters=CR_Socket_Memory
I have set-up:
Procs=4 RealMemory=15360 Socket=1 CoresPerSocket=4 ThreadsPerCore=1
which prevent the usage of HT (at least this is what I think).
Is that a good idea ?
If you want to only allocate one task per core instead of per HT, then yes,
Does selection of CR_Socket_Memory means that Socket will be shared by
different jobs ? or should I enforce --exclusive ?
CR_Socket_Memory prevents more than one job being allocated resources
on a socket
Since my apps are relying strongly on MPI + OpenMP I would like a
socket to be dedicated to a job mpi task. By specifying --ntasks=3 I
get only one socket allocated so I get that in order to enforce my
policy I have to choose:
--ntasks=3 --ntasks-per-socket=1
or
--nodes=3
The first option permits SLURM to schedule the job on more than one
socket per node. The second option forces SLURM to schedule the job
across 3 nodes, which is probably less efficient for your applicationh.
Is that correct ? Is there a better setting ?
Thanks and Best Regards
Guillaume
--
PGP KeyID: 2048R/EA31CFC9 subkeys.pgp.net
