Bureaucrats, cc_docs_admin, cc_staff
2,879
edits
Advanced MPI scheduling: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
command and how its numerous options constrain the placement of processes. | command and how its numerous options constrain the placement of processes. | ||
=== sbatch options affecting process placement === | |||
TO DO: This unorganized list of options should be replaced by an organized discussion. | |||
If it makes sense to explain the terminology, "node", "task", "code", "socket", "cpu", "thread", etc., | |||
it should do so. | |||
* -N, --nodes= | * -N, --nodes= | ||
* -n, --ntasks= | * -n, --ntasks= | ||
| Line 22: | Line 25: | ||
* --mincpus= | * --mincpus= | ||
* --cores-per-socket= | * --cores-per-socket= | ||
* --exclusive[=user|mcs] | * --exclusive[=user|mcs] | ||
* --hint=[compute_bound|memory_bound|multithread|nomultithread] | * --hint=[compute_bound|memory_bound|multithread|nomultithread] | ||
* -m, --distribution=[arbitrary|<block|cyclic|plane] | * -m, --distribution=[arbitrary|<block|cyclic|plane] | ||
* --mem_bind= | * --mem_bind= | ||
You should also understand how memory is controlled: | |||
* --mem= and --mem-per-cpu= | |||
=== Hybrid jobs: MPI and OpenMP, or MPI and threads === | === Hybrid jobs: MPI and OpenMP, or MPI and threads === | ||