Sbatch array job example should include a throttle (i.e. max running tasks)

[flakrat]

What is inaccurate?

Howdy,

We should encourage users to throttle their array jobs. The Practical Examples of sbatch Usage With the --array Flag and Dynamic Indices (and any other array job examples) should include .

Per https://slurm.schedmd.com/job_array.html

A maximum number of simultaneously running tasks from the job array may be specified using a % separator. For example --array=0-15%4 will limit the number of simultaneously running tasks from this job array to 4.

As an aside, an operator can alter an existing array job via scontrol to add a throttle (https://slurm.schedmd.com/scontrol.html):

ArrayTaskThrottle=
Specify the maximum number of tasks in a job array that can execute at the same time. Set the count to zero in order to eliminate any limit. The task throttle count for a job array is reported as part of its ArrayTaskId field, preceded with a percent sign. For example ArrayTaskId=1-10%2 indicates the maximum number of running tasks is limited to 2.

Where is the inaccuracy?

Not an inaccuracy, but an improvement : -) Multiple parts of the https://docs.rc.uab.edu/cheaha/slurm/practical_sbatch/ page provide examples of --array