Re: [slurm-users] number of tasks that can run on a node without oversubscribing

2019-07-12 Thread Juergen Salk
Hallo, the cpu vs. cores vs. threads issues also confused me at the very beginning. Although, in general, we do not encourage our users to make use of hyperthreading, we have decided to leave it enabled in the BIOS as there are some use cases that are known to benefit from hyperthreading. I think

Re: [slurm-users] number of tasks that can run on a node without oversubscribing

2019-07-12 Thread mercan
Hi; If you want to use the threads as cpus, you should set CR_CPU, instead of CR_Core. Regards; Ahmet M. 12.07.2019 21:29 tarihinde mercan yazdı: Hi; You can find the Definitions of Socket, Core, & Thread at: https://slurm.schedmd.com/mc_support.html Your status: CPUs=COREs=Sockets*Cor

Re: [slurm-users] number of tasks that can run on a node without oversubscribing

2019-07-12 Thread mercan
Hi; You can find the Definitions of Socket, Core, & Thread at: https://slurm.schedmd.com/mc_support.html Your status: CPUs=COREs=Sockets*CoresPerSocket=1*4=4 Threads=COREs*ThreadsPerCore=4*2=8 Regards; Ahmet M. 12.07.2019 20:15 tarihinde Hanu Pathuri yazdı: Hi, Here is my node informa

[slurm-users] number of tasks that can run on a node without oversubscribing

2019-07-12 Thread Hanu Pathuri
Hi, Here is my node information. I am confused with the terminology w.r.t CPU vs CORE. NodeName=hpathuri-linux CPUs=8 RealMemory=15833 Sockets=1 CoresPerSocket=4 ThreadsPerCore=2 State=UNKNOWN. I am unable to schedule more than 4 tasks without over subscribing even through my configuration look