Dear Christoph,
On 13.09.19 11:33, Christoph Brüning wrote:
> this seems actually to be related to hyperthreading on Intel CPUs. We
> see the same behaviour on our Xeon Gold 6134 Nodes running Slurm 17.11.
>
> The Slurm FAQ ( https://slurm.schedmd.com/faq.html#cpu_count ) states:
> "Note that eve
Dear René,
this seems actually to be related to hyperthreading on Intel CPUs. We
see the same behaviour on our Xeon Gold 6134 Nodes running Slurm 17.11.
The Slurm FAQ ( https://slurm.schedmd.com/faq.html#cpu_count ) states:
"Note that even on systems with hyperthreading enabled, the resources
Dear all,
recently we upgraded slurm from 18.08.3 to 18.08.7 and we noticed the
following the behaviour:
If we start the following test script:
#!/bin/bash
#SBATCH --job-name=test
#SBATCH --output=test.log
#SBATCH --error=test.err
#SBATCH --ntasks=3
#SBATCH --mem=100M
#SBATCH --qos=high
sleep
