Il 12/08/2016 01:42, Christopher Samuel ha scritto: > The CR_ONE_TASK_PER_CORE is a hold over from then, it means that if > you've got HT/SMT enabled you'll get one MPI rank (Slurm task) per > physical core and that can then use threads to utilise the hardware > thread units. And IIUC that should give the max performance.
> Without it you'll get a rank per thread, which may not be > useful to your code. Can two threads of a single core get allocated to different users' tasks? That would kill performance... I'm trying to make things simple for my users, but that can be quite hard in an heterogeneous cluster like ours... -- Diego Zuccato Servizi Informatici Dip. di Fisica e Astronomia (DIFA) - Università di Bologna V.le Berti-Pichat 6/2 - 40127 Bologna - Italy tel.: +39 051 20 95786 mail: [email protected]
