Re: [slurm-users] Meaning of --cpus-per-task and --mem-per-cpu when SMT processors are used

[Alexander Grund]

Hi Marcus,

see below for the request info

scontrol show config | grep SelectTypeParameters

SelectTypeParameters    = CR_CORE_MEMORY,CR_ONE_TASK_PER_CORE,CR_CORE_DEFAULT_DIST_BLOCK,CR_PACK_NODES

But I would first like to see, what

sbatch -vvv jobscript

outputs first.

salloc: defined options
salloc: -------------------- --------------------
salloc: account             : zihforschung
salloc: cpus-per-task       : 50
salloc: hint                : nomultithread
salloc: mem-per-cpu         : 100
salloc: ntasks              : 1
salloc: partition           : ml
salloc: time                : 00:10:00
salloc: verbose             : 3
salloc: -------------------- --------------------
salloc: end of defined options
salloc: debug2: spank: spank_cloud.so: init_post_opt = 0
salloc: debug2: spank: spank_beegfs.so: init_post_opt = 0
salloc: debug2: spank: spank_nv_gpufreq.so: init_post_opt = 0
salloc: debug:  Entering slurm_allocation_msg_thr_create()
salloc: debug:  port from net_stream_listen is 36988
salloc: debug:  Entering _msg_thr_internal
salloc: debug:  Munge authentication plugin loaded
salloc: select/cons_tres loaded with argument 4884
salloc: Cray/Aries node selection plugin loaded

salloc: Linear node selection plugin loaded with argument 4884

salloc: debug2: slurm_allocation_msg_thr_destroy: clearing up message thread
salloc: Job allocation 18847818 has been revoked.
salloc: debug2:   false, shutdown
salloc: debug:  Leaving _msg_thr_internal
salloc: debug2: spank: spank_cloud.so: exit = 0
salloc: debug2: spank: spank_nv_gpufreq.so: exit = 0




--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Alexander Grund
Interdisziplinäre Anwendungsunterstützung und Koordination (IAK)

Technische Universität Dresden
Zentrum für Informationsdienste und Hochleistungsrechnen (ZIH)
Würzburger Str.35/Chemnitzer Str.50, Raum 010 01062 Dresden
Tel.: +49 (351) 463-35982
E-Mail: alexander.gr...@tu-dresden.de
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

salloc: Consumable Resources (CR) Node Selection plugin loaded with argument 4884 salloc: debug2: eio_message_socket_accept: got message connection from 10.1.129.243:49746 8 salloc: error: Job submit/allocate failed: Requested node configuration is not available So good idea, seems someone defined "SLURM_HINT=nomultithread" in all users env. Removing that makes the allocation succeed.

smime.p7s
Description: S/MIME Cryptographic Signature