On Saturday, 22 September 2018 2:35:34 PM AEST Ryan Novosielski wrote:
> We constrain using cgroups, and occasionally someone will request 1
> core (-n1 -c1) and then run something that asks for way more
> cores/threads, or that tries to use the whole machine. They won't
> succeed obviously. Is th
Anecdotally, I’ve had a user cause load averages of 10x the node’s core count.
The user caught it and cancelled the job before I noticed it myself. Where I’ve
seen it happen live on less severe cases, I’ve never noticed anything other
than the excessive load average. Viewed from ‘top’, the offen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/21/2018 11:22 PM, Chris Samuel wrote:
> On Saturday, 22 September 2018 2:53:58 AM AEST Nicolas Bock wrote:
>
>> shows as requesting 1 CPU when in queue, but then allocates all
>> CPU cores once running. Why is that?
>
> Do you mean that Slurm
On Saturday, 22 September 2018 2:53:58 AM AEST Nicolas Bock wrote:
> shows as requesting 1 CPU when in queue, but then allocates all
> CPU cores once running. Why is that?
Do you mean that Slurm expands the cores requested to all the cores on the
node or allocates the node in exclusive mode, or
sk.
Thank you.
-Original Message-
From: slurm-users On Behalf Of DENOU,
MEHDI
Sent: Friday, September 21, 2018 1:17 PM
To: Slurm User Community List ; slurm-users
Subject: Re: [slurm-users] Job allocating more CPUs than requested
Hello Nick,
What is the result with only -n 1 ?
Co
ards,
-Original Message-
From: slurm-users On Behalf Of Nicolas
Bock
Sent: Friday, September 21, 2018 6:54 PM
To: slurm-users
Subject: [slurm-users] Job allocating more CPUs than requested
Hi,
A job run with
sbatch --ntasks=1 \
--ntasks-per-node=1 \
--cpus-per-task=1 \
Hi,
A job run with
sbatch --ntasks=1 \
--ntasks-per-node=1 \
--cpus-per-task=1 \ --ntasks-per-core=1 \
--sockets-per-core=1 \
--cores-per-socket=1 \
--threads-per-core=1
shows as requesting 1 CPU when in queue, but then allocates all
CPU cores once running. Why is that?
Any s
