...
| Code Block | ||
|---|---|---|
| ||
#SBATCH --account=<account> # Your account #SBATCH --partition=<partition> # Slurm Partition; Default: smp #SBATCH --time=<time> # time limit for job; Default: 0:30:00 #SBATCH --qos=<QOS> # Slurm QOS; Default: short30min #SBATCH --nodes=<#Nodes> # Number of nodes #SBATCH --ntasks=<#Tasks> # Number of tasks (MPI) tasks to be launched #SBATCH --mem=<memory> # If more than the default memory is needed; # Default: <#Cores> * <mem per node>/<cores per node> #SBATCH --ntasks-per-node=<ntasks> # Numer of tasks per node #SBATCH --mail-user=<email adress> # Your mail adress if you want to get notifications #SBATCH --mail-type=<email type> # Valid type values are NONE, BEGIN, END, FAIL, REQUEUE, ALL #SBATCH --job-name=<jobname> # Job name #SBATCH --output=<filename_pattern> # File where the standard output is written to(*) #SBATCH --error=<filename_pattern> # File where the error messages are written to(*) |
...
For the job scheduling, Slurm assigns each job a priority, which is calculated based on several factors (Multifactor Priority Plugin). Jobs with higher priority, run first. (In principle – the backfill scheduling plugin helps making best use of available resources by filling up resources that are reserved (and thus idle) for large (high higher priority ) jobs with small (lower priority) jobs.)
On Albedo, Slurm is configured such, that the priority is mainly influenced by the Fairshare factor (which is based on the user’s recent use of resources; see Fairshare (TODO: Link)), while favoring short jobs (with qos=short30min). With longer waiting time in the queue, a job’s priority increases. Job size, partitions or associations are not directly taken into account.
...