I think that you want to use the output of slurmd -C, but if that isn’t telling you the truth then you may not have built slurm with the correct libraries. I believe that you need to build with hwloc in order to get the most accurate details of the CPU topology. Make sure you have hwloc-devel installed and try to rebuild Slurm.
Mike Robbert From: slurm-users <slurm-users-boun...@lists.schedmd.com> on behalf of David Henkemeyer <david.henkeme...@gmail.com> Date: Wednesday, April 28, 2021 at 16:37 To: slurm-users@lists.schedmd.com <slurm-users@lists.schedmd.com> Subject: [External] [slurm-users] slurmd -C vs lscpu - which do I use to populate slurm.conf? CAUTION: This email originated from outside of the Colorado School of Mines organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe. I'm working on populating slurm.conf on my nodes, and I noticed that slurmd -C doesn't agree with lscpu, in all cases, and I'm not sure why. Here is what lscpu reports: Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 And here is what slurmd -C is reporting: NodeName=devops2 CPUs=4 Boards=1 SocketsPerBoard=1 CoresPerSocket=4 ThreadsPerCore=1 RealMemory=9913 Why is there a discrepancy? Which should I use to populate slurm.conf? The OS of this machine is Centos 8. Thank you, David
