...
Content
| Inhalt |
|---|
Slurm partitions
To match your job requirements to the hardware you can choose among the
- Compute cluster of Lise which are linked to their
- charge rates on the page Accounting.
Parameters
...
-p <name>
...
# CPUs per task
...
Important slurm commands
The commands normally used for job control and management are
- Job submission:
sbatch <jobscript>srun <arguments> <command> - Job status of a specific job:
squeue -j jobIDfor queues/running jobs$ scontrol show job jobIDfor full job information (even after the job finished).
- Job cancellation:
scancel jobIDscancel -i -u $USERcancel all your jobs (-u $USER) but ask for every job (-i)scancel -9send killSIGKILLinstead ofSIGTERM
- Job overview:
$ squeue -l --me - Job start (estimated):
squeue --start -j jobID - Workload overview of the whole system:
sinfo(esp.sinfo --format="%25C %A") ,squeue -l
Job Scripts
A job script can be any script that contains special instruction for Slurm. Most commonly used forms are shell scripts, such as bash or plain sh. But other scripting languages (e.g. Python, Perl, R) are also possible.
...
More examples can be found at Examples and Recipes.
Parameters
Interactive Jobs
See according Section in the Quick Start Guide.
Important slurm commands
The commands normally used for job control and management are
- Job submission:
sbatch <jobscript>srun <arguments> <command> - Job status of a specific job:
squeue -j jobIDfor queues/running jobs$ scontrol show job jobIDfor full job information (even after the job finished).
- Job cancellation:
scancel jobIDscancel -i -u $USERcancel all your jobs (-u $USER) but ask for every job (-i)scancel -9send killSIGKILLinstead ofSIGTERM
...
| Parameter | SBATCH flag | Comment |
|---|---|---|
| # nodes | -N <#> | |
| # tasks | -n <#> | |
| # tasks per node | #SBATCH --tasks-per-node <#> | Different defaults between mpirun and srun |
| partition | -p <name> | standard96 (Lise), medium40 (Emmy) |
# CPUs per task | -c <#> | interesting for OpenMP/Hybrid jobs |
| Wall time limit | -t hh:mm:ss | |
| --mail-type=ALL | See sbatch manpage for different types | |
| Project/Account | -A <project> | Specify project for NPL accounting |
Interactive Jobs
See according Section in the Quick Start Guide.
Using the Shared Nodes
We provide a varying number of nodes from the large40 and large96 partitions as post processeing nodes in a shared mode, so that multiple jobs can run at once on a single node. You can request CPUs and memory and should take care, that you do not exceed your limits. For each CPU/Hyperthread, there is about 9.6Gb of Memory on large40:shared or 4 on the large96:shared partition.
...
Slurm offers a lot of options for job allocation, process placement, job dependencies and arrays and much more. We cannot exhaustively cover all topics here. As mentioned at the top of the page, please consult the official slurm documentation and the man pages for an in depth description of all parameters.
...