[ Skip to the content ]

Institute of Formal and Applied Linguistics Wiki


[ Back to the navigation ]

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
gpu [2018/10/10 16:48]
fucik
gpu [2018/11/28 11:21]
laitoch [Rules]
Line 7: Line 7:
 | machine | GPU type | GPU driver version | [[https://en.wikipedia.org/wiki/CUDA#GPUs_supported|cc]] | GPU cnt | GPU RAM (GB) | machine RAM (GB)| AVX | | machine | GPU type | GPU driver version | [[https://en.wikipedia.org/wiki/CUDA#GPUs_supported|cc]] | GPU cnt | GPU RAM (GB) | machine RAM (GB)| AVX |
 | dll1 |  GeForce GTX 1080 |  396.24 |  6.1 |  8 |  8 |  249 | yes | | dll1 |  GeForce GTX 1080 |  396.24 |  6.1 |  8 |  8 |  249 | yes |
-| dll2 |  GeForce GTX 1080 |  396.24 |  6.1 |  8 |  8 |  249 | yes |+| dll2 (out of order) |  GeForce GTX 1080 |  396.24 |  6.1 |  8 |  8 |  249 | yes |
 | dll3 |  GeForce GTX 1080 Ti |  396.24 |  6.1 |  10 |  11 |  249 | yes | | dll3 |  GeForce GTX 1080 Ti |  396.24 |  6.1 |  10 |  11 |  249 | yes |
 | dll4 |  GeForce GTX 1080 Ti |  396.24 |  6.1 |  10 |  11 |  249 | yes | | dll4 |  GeForce GTX 1080 Ti |  396.24 |  6.1 |  10 |  11 |  249 | yes |
Line 26: Line 26:
 Multiple versions of CUDA library are accessible on each machine together with cudnn. Theano and TensorFlow is supported. Multiple versions of CUDA library are accessible on each machine together with cudnn. Theano and TensorFlow is supported.
  
-[[https://ufaladm2.ufal.hide.ms.mff.cuni.cz/munin/ufal.hide.ms.mff.cuni.cz/lrc-master.ufal.hide.ms.mff.cuni.cz/index.html#dll|GPU usage rolling graphs]]+[[http://ufaladm2.ufal.hide.ms.mff.cuni.cz/munin/ufal.hide.ms.mff.cuni.cz/lrc-master.ufal.hide.ms.mff.cuni.cz/index.html#dll|GPU usage rolling graphs]]
  
  
Line 34: Line 34:
   * Always specify the number of GPU cards (e.g. ''gpu=1''), the minimal Cuda capability you need (e.g. ''gpu_cc_min3.5=1'') and your GPU memory requirements (e.g. ''gpu_ram=2G''). Thus e.g. <code>qsub -q gpu-ms.q -l gpu=1,gpu_cc_min3.5=1,gpu_ram=2G</code>   * Always specify the number of GPU cards (e.g. ''gpu=1''), the minimal Cuda capability you need (e.g. ''gpu_cc_min3.5=1'') and your GPU memory requirements (e.g. ''gpu_ram=2G''). Thus e.g. <code>qsub -q gpu-ms.q -l gpu=1,gpu_cc_min3.5=1,gpu_ram=2G</code>
   * If you need more than one GPU card (on a single machine), always require as many CPU cores (''-pe smp X'') as many GPU cards you need. E.g. <code>qsub -q gpu-ms.q -l gpu=4,gpu_cc_min3.5=1,gpu_ram=7G -pe smp 4</code> **Warning**: currently, this does not work, so you can omit the ''-pe smp X'' part. Milan Fučík is working on a fix.   * If you need more than one GPU card (on a single machine), always require as many CPU cores (''-pe smp X'') as many GPU cards you need. E.g. <code>qsub -q gpu-ms.q -l gpu=4,gpu_cc_min3.5=1,gpu_ram=7G -pe smp 4</code> **Warning**: currently, this does not work, so you can omit the ''-pe smp X'' part. Milan Fučík is working on a fix.
-  * For interactive jobs, you can use ''qrsh'', but make sure to end your job as soon as you don't need the GPU (so don't use qrsh for long training). **Warning: ''-pty yes bash'' is necessary**, otherwise the variable ''$CUDA_VISIBLE_DEVICES'' will not be set correctly. E.g. <code>qrsh -q gpu-ms.q -l gpu=1,gpu_ram=2G -pty yes bash</code>In general: don't reserve a GPU (as described above) without actually using it for longer time. (E.g. try separating steps which need GPU and steps which do not and execute those separately on our GPU resp. CPU cluster.) Ondřej Bojar has a script /home/bojar/tools/servers/watch_gpus for watching reserved but unused GPU on most machines which will e-mail you, but don't rely on in only.+  * For interactive jobs, you can use ''qrsh'', but make sure to end your job as soon as you don't need the GPU (so don't use qrsh for long training). **Warning: ''-pty yes bash -l'' is necessary**, otherwise the variable ''$CUDA_VISIBLE_DEVICES'' will not be set correctly. E.g. <code>qrsh -q gpu-ms.q -l gpu=1,gpu_ram=2G -pty yes bash -l</code>In general: don't reserve a GPU (as described above) without actually using it for longer time. (E.g. try separating steps which need GPU and steps which do not and execute those separately on our GPU resp. CPU cluster.) Ondřej Bojar has a script /home/bojar/tools/servers/watch_gpus for watching reserved but unused GPU on most machines which will e-mail you, but don't rely on it only.
   * Note that the dll machines have typically 10 cards, but "just" 250 GB RAM (DLL6 has only 128 GB). So the expected (maximal) ''mem_free'' requirement for jobs with 1 GPU is 25GB. If your 1-GPU job takes e.g. 80 GB and you submit three such jobs on the same machine, you have effectively blocked the whole machine and seven GPUs remain unused. If you really need to submit more high-memory jobs, send each on a different machine.   * Note that the dll machines have typically 10 cards, but "just" 250 GB RAM (DLL6 has only 128 GB). So the expected (maximal) ''mem_free'' requirement for jobs with 1 GPU is 25GB. If your 1-GPU job takes e.g. 80 GB and you submit three such jobs on the same machine, you have effectively blocked the whole machine and seven GPUs remain unused. If you really need to submit more high-memory jobs, send each on a different machine.
  
Line 93: Line 93:
   qsubmit --gpumem=2G --queue="gpu-ms.q" WHAT_SHOULD_BE_RUN   qsubmit --gpumem=2G --queue="gpu-ms.q" WHAT_SHOULD_BE_RUN
      
-It is recommended to use priority lower than the default -100 if you are not rushing for the results and don't need to leap over your colleagues jobs.+It is recommended to use priority lower than the default -100 if you are not rushing for the results and don't need to leap over your colleagues jobs. Please, do not use priority between -99 to 0 for jobs taking longer than a few hours, unless it is absolutely necessary for your work.
 ==== Basic commands ==== ==== Basic commands ====
  

[ Back to the navigation ] [ Back to the content ]