Il 12/10/20 05:55, William Brown ha scritto:
> We always disable hyper-threading on the compute nodes, at the
> recommendation of the company that installed it, who reported that it
> ran faster that way. Multi-threading has a cost and is not ideal for
> compute workloads. It is better for thing
October 2020 01:14
To: Slurm User Community List
Subject: Re: [slurm-users] unable to run on all the logical cores
Indeed, it makes sense now. However, if I launch many R processes using the
"parallel" package, I can easily have all the "logical" cores running. In the
On 10/7/20 10:13 pm, David Bellot wrote:
NodeName=foobar01 CPUs=80 Boards=1 SocketsPerBoard=2 CoresPerSocket=20
ThreadsPerCore=2 RealMemory=257243 State=UNKNOWN
With this configuration Slurm is allocation a single physical core (with
2 thread units) per task. So you are using all (physical) c
Indeed, it makes sense now. However, if I launch many R processes using the
"parallel" package, I can easily have all the "logical" cores running. In
the background, if I'm correct ,R will "fork" and not create a thread. So
we have independent processes. On a 20 cores CPU for example, I have 40
"lo
R is single threaded.
On Thu, 8 Oct 2020, 07:44 Diego Zuccato, wrote:
> Il 08/10/20 08:19, David Bellot ha scritto:
>
> > good spot. At least, scontrol show job is now saying that each job only
> > requires one "CPU", so it seems all the cores are treated the same way
> now.
> > Though I still h
Il 08/10/20 08:19, David Bellot ha scritto:
> good spot. At least, scontrol show job is now saying that each job only
> requires one "CPU", so it seems all the cores are treated the same way now.
> Though I still have the problem of not using more than half the cores.
> So I suppose it might be du
Hi Rodrigo,
good spot. At least, scontrol show job is now saying that each job only
requires one "CPU", so it seems all the cores are treated the same way now.
Though I still have the problem of not using more than half the cores. So I
suppose it might be due to the way I submit (batchtools in thi
Hi David,
I had the same problem time ago when configuring my first server.
Could you try SelectTypeParameters=CR_CPU instead of
SelectTypeParameters=CR_Core?
Best regards,
Rodrigo.
On Thu, Oct 8, 2020, 02:16 David Bellot
wrote:
> Hi,
>
> my Slurm cluster has a dozen machines configured as fo
Hi,
my Slurm cluster has a dozen machines configured as follows:
NodeName=foobar01 CPUs=80 Boards=1 SocketsPerBoard=2 CoresPerSocket=20
ThreadsPerCore=2 RealMemory=257243 State=UNKNOWN
and scheduling is:
# SCHEDULING
SchedulerType=sched/backfill
SelectType=select/cons_tres
SelectTypeParameters=
