[slurm-users] How should I do so that jobs are allocated to the thread and not to the core ?

Jean-mathieu CHANTREIN jean-mathieu.chantrein at univ-angers.fr
Mon May 6 15:12:33 UTC 2019


Hello, 

Thank you for your answers. 

I did not succeed to make the faq proposal (Question 30 note). I think I succeeded by cheating like this: 

NodeName=DEFAULT Boards=1 SocketsPerBoard=2 CoresPerSocket=36 ThreadsPerCore=1 RealMemory=128000 

Regards. 

Jean-Mathieu 

> De: "Doug Meyer" <dameyer at raytheon.com>
> À: "Slurm User Community List" <slurm-users at lists.schedmd.com>
> Envoyé: Jeudi 2 Mai 2019 16:15:30
> Objet: Re: [slurm-users] How should I do so that jobs are allocated to the
> thread and not to the core ?

> Had same problem in slurm 15, not sure if it affects newer versions. Don’t use
> the expanded node definition

> NodeName = DEFAULT Boards = 1 SocketsPerBoard = 2 CoresPerSocket = 18
> ThreadsPerCore = 2 RealMemory = 128000

> Use the simpler

> NodeName=DEFAULT Cores=36 RealMemory = 128000

> Slurm will use both logical threads and not just the physical.

> Doug

> “To err is human – and to blame it on a computer is even more so.” Robert Orben

> From: slurm-users <slurm-users-bounces at lists.schedmd.com> On Behalf Of Benjamin
> Redling
> Sent: Thursday, May 2, 2019 3:49 AM
> To: Slurm User Community List <slurm-users at lists.schedmd.com>
> Subject: [External] Re: [slurm-users] How should I do so that jobs are allocated
> to the thread and not to the core ?

> Have you Seen the slurm FAQ?
> You may want to search on that site for "Hyperthreading"

> (Sorry for the TOFU. vacation, mobile)

> Am 30. April 2019 18:07:03 MESZ schrieb Jean-mathieu CHANTREIN < [
> mailto:jean-mathieu.chantrein at univ-angers.fr |
> jean-mathieu.chantrein at univ-angers.fr ] >:
>> Hello,

>> Most jobs of my users are single-thread. I have multithreaded processors. The
>> jobs seem to reserve 2 logical CPU (1 core=2 CPU (2 threads)) whereas it only
>> uses 1 logical CPU(1 thread). Nevertheless, my slurm.conf file indicates:

>> [...]
>> SelectType = select / cons_res
>> SelectTypeParameters = CR_CPU
>> FastSchedule = 1
>> [...]
>> NodeName = DEFAULT Boards = 1 SocketsPerBoard = 2 CoresPerSocket = 18
>> ThreadsPerCore = 2 RealMemory = 128000

>> And here is an excerpt from the output of a job running on this type of node:
>> $ scontrol show job idjob

>> [...]

>> NumNodes=1 NumCPUs=1 NumTasks=1 CPUs/Task=1 ReqB:S:C:T=0:0:*:*
>> TRES=cpu=1,mem=200M,node=1,billing=1
>> Socks/Node=* NtasksPerN:B:S:C=0:0:*:* CoreSpec=*
>> MinCPUsNode=1 MinMemoryCPU=200M MinTmpDiskNode=0
>> Features=(null) DelayBoot=00:00:00
>> OverSubscribe=OK Contiguous=0 Licenses=(null) Network=(null)

>> But with [ https://github.com/OleHolmNielsen/Slurm_tools/tree/master/pestat |
>> pestat
>>  ] , I can see my node use 72/72 CPU but have only 36 job running like this one.

>> How should I do so that jobs are allocated to the thread and not to the core ?

>> Best regards.

>> Jean-Mathieu



> --
> Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20190506/b0f052f8/attachment.html>


More information about the slurm-users mailing list