[slurm-users] Array jobs vs. many jobs

Ree, Jan-Albert van J.A.v.Ree at marin.nl
Fri Nov 22 21:39:56 UTC 2019

Jan-Albert van Ree  | Linux System Administrator | Digital Services
MARIN | T +31 317 49 35 48 | mailto:J.A.v.Ree at marin.nl | http://www.marin.nl

It helps a lot indeed ; we run arrays up to 100k elements and more. If you submit 100k separate jobs, the scheduler will definately grind to a halt.


From: slurm-users <slurm-users-bounces at lists.schedmd.com> on behalf of Ryan Novosielski <novosirj at rutgers.edu>
Sent: Friday, November 22, 2019 21:18
To: slurm-users at lists.schedmd.com
Subject: [slurm-users] Array jobs vs. many jobs

Hi there,

Quick question that I'm not sure how to find the answer to otherwise: do array jobs have less impact on the scheduler in any way than a whole long list of jobs run the more traditional way? Less startup overhead, anything like that?


(we run 17.11 on CentOS 7, but I'm not sure it makes any difference here)

More information about the slurm-users mailing list