cc_staff
153
edits
What is a scheduler?: Difference between revisions
Marked this version for translation
mNo edit summary |
(Marked this version for translation) |
||
| Line 21: | Line 21: | ||
It runs the programs <code>echo</code> and <code>sleep</code>, there is no input, and the output will go to a default location. Lines starting with <code>#SBATCH</code> are directives to the scheduler, telling it things about what the job needs to run. This job, for example, only needs one minute of run time (00:01:00). | It runs the programs <code>echo</code> and <code>sleep</code>, there is no input, and the output will go to a default location. Lines starting with <code>#SBATCH</code> are directives to the scheduler, telling it things about what the job needs to run. This job, for example, only needs one minute of run time (00:01:00). | ||
== The job scheduler == | == The job scheduler == <!--T:4--> | ||
The job scheduler is a piece of software with multiple responsibilities. It must | The job scheduler is a piece of software with multiple responsibilities. It must | ||
* maintain a database of jobs, | * maintain a database of jobs, | ||
| Line 64: | Line 64: | ||
will change the time limit of the job to 30 minutes. Any option can be overridden in this way. | will change the time limit of the job to 30 minutes. Any option can be overridden in this way. | ||
==Choosing where the output goes== | ==Choosing where the output goes== <!--T:13--> | ||
If you want the output file to have a more distinctive name than <code>slurm‑1234.out</code>, you can use <code>--output</code> to change it. | If you want the output file to have a more distinctive name than <code>slurm‑1234.out</code>, you can use <code>--output</code> to change it. | ||
The following script sets a ''job name'' which will appear in <code>squeue</code> output, and sends the output to a file prefixed with the job name and containing the job ID number. | The following script sets a ''job name'' which will appear in <code>squeue</code> output, and sends the output to a file prefixed with the job name and containing the job ID number. | ||
| Line 83: | Line 83: | ||
Error output will normally appear in the same file, just as it would if you were typing commands interactively. If you wish you can split the standard error channel (stderr) from the standard output channel (stdout) by specifying a file name with the <code>‑e</code> option. | Error output will normally appear in the same file, just as it would if you were typing commands interactively. If you wish you can split the standard error channel (stderr) from the standard output channel (stdout) by specifying a file name with the <code>‑e</code> option. | ||
==Accounts and projects== | ==Accounts and projects== <!--T:16--> | ||
Information about your job, like how long it waited, how long it ran, and how many cores it used, is recorded so we can monitor our quality of service and so we can report to our funders how their money is spent. Every job must have an associated ''account name'' corresponding to a Compute Canada [https://ccdb.computecanada.ca/me/faq#what_is_rap resource allocation project]. | Information about your job, like how long it waited, how long it ran, and how many cores it used, is recorded so we can monitor our quality of service and so we can report to our funders how their money is spent. Every job must have an associated ''account name'' corresponding to a Compute Canada [https://ccdb.computecanada.ca/me/faq#what_is_rap resource allocation project]. | ||