Advanced MPI scheduling: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 181: Line 181:


<!--T:13-->
<!--T:13-->
In programming terminology, <code>srun</code> is at a higher level of abstraction than <code>mpirun</code>. Anything that can be done with <code>mpirun</code> can be done with <code>srun</code>, and more. It is the tool in Slurm to distribute any kind of computations. It replaces Torque’s <code>pbsdsh</code>, for example, and much more. Think of <code>srun</code> as the SLURM <i>all-around parallel-tasks distributor</i>; once a particular set of resources is allocated, the nature of your application doesn't matter (MPI, OpenMP, hybrid, serial farming, pipelining, multiprogram, etc.), you just have to <code>srun</code> it
In programming terms, <code>srun</code> is at a higher level of abstraction than <code>mpirun</code>. Anything that can be done with <code>mpirun</code> can be done with <code>srun</code>, and more. It is the tool in Slurm to distribute any kind of computations. It replaces Torque’s <code>pbsdsh</code>, for example, and much more. Think of <code>srun</code> as the SLURM <i>all-around parallel-tasks distributor</i>; once a particular set of resources is allocated, the nature of your application doesn't matter (MPI, OpenMP, hybrid, serial farming, pipelining, multiprogram, etc.), you just have to <code>srun</code> it


<!--T:14-->
<!--T:14-->
rsnt_translations
56,426

edits