...
and RawUsage= cpu-seconds (#CPUs * seconds). → Jobs using the 48h
QOS are twice as expensive when calculating job priorities (see Scheduling (TODO: Link)).
Specifying job resources
Job resources are defined at the header of your job script (or as command line arguments for sbatch
or salloc
). A full list see https://slurm.schedmd.com/sbatch.html#SECTION_OPTIONS. Here is a list of the most common ones:
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: short
#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 filename patterns see: https://slurm.schedmd.com/sbatch.html#SECTION_%3CB%3Efilename-pattern%3C/B%3E
Example Scripts
Job arrays
...