Slurm is the batch system available. Any script can be submitted as a job with no changes, but you might want to see Writing SLURM jobs to customise it.
To submit a script as a serial job with default options enter the command:
sbatch yourscript.sh |
You may query the queues to see the jobs currently running or pending with:
squeue |
And cancel a job with
scancel <jobid> |
The "scancel" command should be executed on a login node on the same cluster as the job. |
See the Slurm documentation for more details on the different commands available to submit, query or cancel jobs.
These are the different QoS (or queues) available for standard users on the four complexes:
QoS name | Type | Suitable for... | Shared nodes | Maximum jobs per user | Default / Max Wall Clock Limit | Default / Max CPUs | Default / Max Memory |
---|---|---|---|---|---|---|---|
nf | fractional | serial and small parallel jobs. It is the default | Yes | - | average runtime + standard deviation / 2 days | 1 / 64 | 8 GB / 128 GB |
np | parallel | parallel jobs requiring more than half a node | No | - | average runtime + standard deviation / 2 days | - | 240GB / 240 GB per node (all usable memory in a node) |
On the AC complex you will find dedicated queues for special partition with GPU-enabled nodes. See HPC2020: GPU usage for AI and Machine Learning for all the details on how to make use of those special resources.
|
For those using ECS, these are the different QoS (or queues) available for standard users of this service:
QoS name | Type | Suitable for... | Shared nodes | Maximum jobs per user | Default / Max Wall Clock Limit | Default / Max CPUs | Default / Max Memory |
---|---|---|---|---|---|---|---|
ef | fractional | serial and small parallel jobs - ECGATE service | Yes | - | average job runtime + standard deviation / 2 days | 1 / 8 | 8 GB / 16 GB |
el | long | serial and small parallel interactive jobs - ECGATE service | Yes | - | average job runtime + standard deviation / 7 days | 1 / 8 | 8 GB / 16 GB |
et | Time-critical Option 1 | serial and small parallel Time-Critical jobs. Only usable through ECACCESS Time Critical Option-1 | Yes | - | average job runtime + standard deviation / 12 hours | 1 / 8 | 8 GB / 16 GB |
Using the "ecinteractive" command, jobs will be submitted in either of these queues depending on if the user has access to the full HPC service (ni queue, for Member State users) or the ECS service (ei queue, for co-operating States, as service previously known as ECGATE)
|
See HPC2020: Job Runtime Management for more information on how the default Wall Clock Time limit is calculated. |
Different limits on the different QoSs may be introduced or changed as the system evolves. |
If you want to get all the details of a particular QoS on the system, you may run, for example:
|
If you are submitting jobs from a different platform via ssh, please use the *-batch dedicated nodes instead of the *-login equivalents:
For example, to submit a job from a remote platform onto the Atos HCPF:
ssh hpc-batch "sbatch myjob.sh" |
<style> div#content h2 a::after { content: " - [read more]"; } </style> |