Hello Patrick,
Yeah I'd recommend upgrading, and I imagine most others will, too. I have
found with Slurm that upgrades are nearly mandatory, at least annually or
so, mostly because it's more challenging to upgrade from much older
versions and requires bootstrapping. Not sure about the minus sign;
Hi Benjamin,
Yes, I saw this on an archived discussion too and I've added these
parameters. A little bit tricky to do as my setup is deployed via
Ansible. But with this setup I'm not able to request a GPU at all. All
these test are failing and slurm do not accept the job:
srun -n 1 -p tenibr
Hi Patrick,
You're missing a Gres= on your node in your slurm.conf:
Nodename=tenibre-gpu-0 RealMemory=257270 Sockets=2 CoresPerSocket=16
ThreadsPerCore=1 State=UNKNOWN Gres=gpu:A100-40:1,gpu:A100-80:1
Ben
On 13/11/2024 16:00, Patrick Begou via slurm-users wrote:
This email was sent to you by
Le 13/11/2024 à 15:45, Roberto Polverelli Monti via slurm-users a écrit :
Hello Patrick,
On 11/13/24 12:01 PM, Patrick Begou via slurm-users wrote:
As using this GPU resource increase I would like to manage this
resource with Gres to avoid usage conflict. But at this time my setup
do not works
Hello Patrick,
On 11/13/24 12:01 PM, Patrick Begou via slurm-users wrote:
As using this GPU resource increase I would like to manage this resource
with Gres to avoid usage conflict. But at this time my setup do not
works as I can reach a GPU without reserving it:
srun -n 1 -p tenibre-gpu
