Commit ab0aded9 authored by Giuseppe Fiameni's avatar Giuseppe Fiameni
Browse files

Update README.md

parent 2e833508
......@@ -40,7 +40,7 @@ Simple submission script
The job then enters the queue in the **PENDING** state. Once resources become available and the job has highest priority, an allocation is created for it and it goes to the **RUNNING** state. If the job completes correctly, it goes to the **COMPLETED** state, otherwise, it is set to the **FAILED** state.
Interestingly, you can get near-realtime information about your running program (memory consumption, etc.) with the sstat command, by introducing sstat -j jobid. You can select what you want sstat to output with the --format parameter. Refer to the manpage for more information man sstat.
Interestingly, you can get near-realtime information about your running program (memory consumption, etc.) with the `sstat` command, by introducing `sstat -j jobid`. You can select what you want sstat to output with the `--format` parameter. Refer to the manpage for more information `man sstat`.
Upon completion, the output file contains the result of the commands run in the script file. In the above example, you can see it with `cat res.out` command.
......@@ -55,9 +55,9 @@ There are several ways a parallel job, one whose tasks are run simultaneously, c
* by running several instances of a single-threaded program (so-called embarrassingly parallel paradigm or a job array)
* by running one master program controlling several slave programs (master/slave paradigm)
In the Slurm context, a task is to be understood as a process. So a multi-process program is made of several tasks. By contrast, a multithreaded program is composed of only one task, which uses several CPUs.
In the SLURM context, a task is to be understood as a process. So a multi-process program is made of several tasks. By contrast, a multithreaded program is composed of only one task, which uses several CPUs.
Tasks are requested/created with the `--ntasks` option, while CPUs, for the multithreaded programs, are requested with the `--cpus-per-task` option. Tasks cannot be split across several compute nodes, so requesting several CPUs with the --cpus-per-task option will ensure all CPUs are allocated on the same compute node. By contrast, requesting the same amount of CPUs with the `--ntasks` option may lead to several CPUs
Tasks are requested/created with the `--ntasks` option, while CPUs, for the multithreaded programs, are requested with the `--cpus-per-task` option. Tasks cannot be split across several compute nodes, so requesting several CPUs with the `--cpus-per-task` option will ensure all CPUs are allocated on the same compute node. By contrast, requesting the same amount of CPUs with the `--ntasks` option may lead to several CPUs
## More submission script examples
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment