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> |
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:
| 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 | - | 2 day / 2 days | 1 / 64 | 8 GB / 128 GB |
| ef | fractional | serial and small parallel jobs - ECGATE service | Yes | - | 2 day / 2 days | 1 / 8 | 8 GB / 16 GB |
| ni | interactive | serial and small parallel interactive jobs | Yes | 1 | 1 day / 7 days | 1 / 32 | 8 GB / 32 GB |
| ei | interactive | serial and small parallel interactive jobs - ECGATE service | Yes | 1 | 1 day / 7 days | 1 / 4 | 8 GB / 8 GB |
| el | long | serial and small parallel interactive jobs - ECGATE service | Yes | 1 | 7 day / 7 days | 1 / 8 | 8 GB / 16 GB |
| np | parallel | parallel jobs requiring more than half a node | No | - | 2 days / 2 days | - | - |
If you want to get all the details of a particular QoS on the system, you may run, for example:
|
Different limits on the different QoSs may be introduced or changed as the system evolves to its final configuration. |
<style>
div#content h2 a::after {
content: " - [read more]";
}
</style> |