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?
kinda sorta.
I think of array jobs as a bit like Python generat
Hi Ryan,
On 11/22/19 12:18 PM, Ryan Novosielski wrote:
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?
Slu
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.
