I think that's incorrect:
> The concept of hyper-threading is not doubling cores. It is a single
> core that can 'instantly' switch work from one process to another.
> Only one is being worked on at any given time.
A core can have multiple (usually 2) independent execution pipelines, so
that mul
Hi Brian and Hermann,
true. This makes a lot of sense. I will consider setting up Hermann's
configuration, defaulting to "--hint=nomultithread".
Thanks!
Sebastian
On 13.02.23 15:29, Brian Andrus wrote:
Hermann makes a good point.
The concept of hyper-threading is not doubling cores. It is
Hermann makes a good point.
The concept of hyper-threading is not doubling cores. It is a single
core that can 'instantly' switch work from one process to another. Only
one is being worked on at any given time.
So if I request a single core on a hyper-threaded system, I would not be
pleased
Hi Sebastian,
I am glad I could help (although not exactly as expected :-).
With your node-configuration you are "circumventing" how Slurm behaves,
when using "CR_Core": if you read the respective part in
https://slurm.schedmd.com/slurm.conf.html
it says:
"CR_Core
[...] On nodes with hype