Jan-Albert van Ree | Linux System Administrator | Digital Services MARIN | T +31 317 49 35 48 | mailto:j.a.v....@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. Regards, -- Jan-Albert ________________________________________ From: slurm-users <slurm-users-boun...@lists.schedmd.com> on behalf of Ryan Novosielski <novos...@rutgers.edu> Sent: Friday, November 22, 2019 21:18 To: slurm-users@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? Thanks! (we run 17.11 on CentOS 7, but I'm not sure it makes any difference here)