Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
gpu [2017/03/16 17:10] kocmanek [TensorFlow] |
gpu [2017/06/26 16:51] kocmanek [Using cluster] |
||
---|---|---|---|
Line 5: | Line 5: | ||
===== Servers with GPU units ===== | ===== Servers with GPU units ===== | ||
- | | machine | GPU; [[https:// | + | | machine |
- | | titan-gpu | + | | titan | GeForce GTX 1080 Ti; cc6.1 | 1 | 12 GB | | |
- | | twister1 | + | | titan-gpu |
- | | twister2 | + | | twister1; twister2; |
- | | kronos-dev | Tesla K40c; cc3.5 | 1 | 12 GB | | | + | | iridium |
- | | iridium | + | | victoria; arc | GeForce GT 630; cc3.0 | 1 | 2 GB | desktop machine | |
- | | victoria | + | | athena |
- | | arc | GeForce GT 630; cc3.0 | 1 | 2 GB | + | | dll1; dll2 |
- | | athena | + | |
- | | dll1 | GeForce GTX 1080; cc6.1 | 8 | 8 GB each core | | | + | |
- | | dll2 | + | |
not used at the moment: GeForce GTX 570 (from twister2) | not used at the moment: GeForce GTX 570 (from twister2) | ||
Line 70: | Line 67: | ||
For testing and using the cluster interactively you can use qrsh (this should not be used for long running experiments since the console is not closed on the end of the experiment). Following command will assign you a GPU and creates interactive console. | For testing and using the cluster interactively you can use qrsh (this should not be used for long running experiments since the console is not closed on the end of the experiment). Following command will assign you a GPU and creates interactive console. | ||
- | qrsh -q gpu.q -l gpu=1 -pty yes bash | + | qrsh -q gpu.q -l gpu=1, |
| | ||
For running experiments you must use qsub command: | For running experiments you must use qsub command: | ||
Line 80: | Line 77: | ||
qsubmit --gpumem=2G --queue=" | qsubmit --gpumem=2G --queue=" | ||
| | ||
+ | It is recommended to use priority -100 if you are not rushing for the results and don't need to leap over your colleagues jobs. | ||
==== Basic commands ==== | ==== Basic commands ==== | ||
Line 97: | Line 95: | ||
/ | / | ||
# shows CUDA capability etc. | # shows CUDA capability etc. | ||
+ | | ||
+ | === Select GPU device === | ||
+ | |||
+ | Use variable CUDA_VISIBLE_DEVICES to constrain tensorflow to compute only on the selected one. For the use of first GPU use (GPU queue do this for you): | ||
+ | export CUDA_VISIBLE_DEVICES=0 | ||
+ | |||
+ | To list available devices, use: | ||
+ | / | ||
+ | |||
===== Performance tests ===== | ===== Performance tests ===== | ||
* [[http:// | * [[http:// | ||
- | In the following table is the experiment conducted by Tom Kocmi. You can replicate experiment: / | + | In the following table is the experiment conducted by Tom Kocmi. You can replicate experiment: / |
| machine | Setup; CPU/GPU; [[https:// | | machine | Setup; CPU/GPU; [[https:// | ||
| athena | | athena | ||
| dll2 | (2 GPU) GeForce GTX 1080; cc6.1 | | | dll2 | (2 GPU) GeForce GTX 1080; cc6.1 | | ||
+ | | titan | GeForce GTX 1080 Ti | | ||
| dll1 | (2 GPU) GeForce GTX 1080; cc6.1 | | | dll1 | (2 GPU) GeForce GTX 1080; cc6.1 | | ||
| dll2 | (2 GPU) GeForce GTX 1080; cc6.1 | | | dll2 | (2 GPU) GeForce GTX 1080; cc6.1 | | ||
Line 119: | Line 127: | ||
| lucifer4 | | lucifer4 | ||
| victoria | | victoria | ||
- | |||
- | |||
- | ===== Installed toolkits ===== | ||
- | |||
- | //This should mention where each interesting toolkit lives (on a particular machine).// | ||
- | |||