Best practices for job submission: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 102: Line 102:
<translate>
<translate>
<!--T:18-->
<!--T:18-->
* Ultimately, the goal should be to '''ensure that the CPU efficiency of your jobs is very close to 100%''', as measured by the field <code>CPU Efficiency</code> in the output from the <code>seff</code> command.
* Ultimately, the goal should be to <b>ensure that the CPU efficiency of your jobs is very close to 100%</b>, as measured by the field <code>CPU Efficiency</code> in the output from the <code>seff</code> command.
** Any value of CPU efficiency less than 90% is poor and means that your use of whatever software your job executes needs to be improved.
** Any value of CPU efficiency less than 90% is poor and means that your use of whatever software your job executes needs to be improved.


Line 109: Line 109:
<!--T:20-->
<!--T:20-->
The nodes with GPUs are relatively uncommon so that any job which asks for a GPU will wait significantly longer in most cases.
The nodes with GPUs are relatively uncommon so that any job which asks for a GPU will wait significantly longer in most cases.
* Be sure that this GPU you had to wait so much longer to obtain is '''being used as efficiently as possible''' and that it is really contributing to improved performance in your jobs.
* Be sure that this GPU you had to wait so much longer to obtain is <b>being used as efficiently as possible</b> and that it is really contributing to improved performance in your jobs.
** A considerable amount of software does have a GPU option, for example such widely used packages as [[NAMD]] and [[GROMACS]], but only a small part of these programs' functionality has been modified to make use of GPUs. For this reason, it is wiser to '''first test a small sample calculation both with and without a GPU''' to see what kind of speed-up you obtain from the use of this GPU.
** A considerable amount of software does have a GPU option, for example such widely used packages as [[NAMD]] and [[GROMACS]], but only a small part of these programs' functionality has been modified to make use of GPUs. For this reason, it is wiser to <b>first test a small sample calculation both with and without a GPU</b> to see what kind of speed-up you obtain from the use of this GPU.
** Because of the high cost of GPU nodes, a job using '''a single GPU''' should run significantly faster than if it was using a full CPU node.
** Because of the high cost of GPU nodes, a job using <b>a single GPU</b> should run significantly faster than if it was using a full CPU node.
** If your job '''only finishes 5% or 10% more quickly with a GPU, it's probably not worth''' the effort of waiting to get a node with a GPU as it will be idle during much of your job's execution.
** If your job <b>only finishes 5% or 10% more quickly with a GPU, it's probably not worth</b> the effort of waiting to get a node with a GPU as it will be idle during much of your job's execution.
* '''Other tools for monitoring the efficiency''' of your GPU-based jobs include <code>[https://developer.nvidia.com/nvidia-system-management-interface nvidia-smi]</code>, <code>nvtop</code> and, if you're using software based on [[TensorFlow]], the [[TensorFlow#TensorBoard|TensorBoard]] utility.
* <b>Other tools for monitoring the efficiency</b> of your GPU-based jobs include <code>[https://developer.nvidia.com/nvidia-system-management-interface nvidia-smi]</code>, <code>nvtop</code> and, if you're using software based on [[TensorFlow]], the [[TensorFlow#TensorBoard|TensorBoard]] utility.


==Avoid wasting resources== <!--T:21-->
==Avoid wasting resources== <!--T:21-->
rsnt_translations
57,772

edits

Navigation menu