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 [2016/11/15 16:01] kocmanek |
gpu [2017/08/28 14:40] kocmanek [Set-up CUDA and CUDNN] |
||
---|---|---|---|
Line 4: | Line 4: | ||
===== Servers with GPU units ===== | ===== Servers with GPU units ===== | ||
+ | GPU cluster '' | ||
- | | machine | GPU; [[https:// | + | | machine |
- | | titan-gpu | + | | iridium |
- | | twister1 | + | | titan-gpu |
- | | twister2 | + | | twister1; twister2; |
- | | kronos-dev | Tesla K40c; cc3.5 | + | | dll1; dll2 | GeForce GTX 1080 |
- | | iridium | + | | titan |
- | | victoria | + | | dll3; dll4; dll5 | GeForce |
- | | arc | + | |
- | | athena | + | |
- | not used at the moment: GeForce GTX 570 (from twister2) | + | Desktop machines: |
+ | | machine | ||
+ | | victoria; arc | GeForce GT 630 | cc3.0 | 1 | 2 GB | desktop machine | | ||
+ | | athena | ||
- | Summary of future plans: | + | Not used at the moment: GeForce GTX 570 (from twister2) |
- | * Current Troja servers won't get any GPUs (the only option would be [[http:// | + | All machines |
- | * The old Quadro K2000 we have is a much more low end piece, so we can't test is in Troja. | + | |
- | * There is MetaCentrum which also has GPUs, so testing can be done there. | + | |
- | * It is impossible (wasteful in terms of space and forbidden by a dean regulation) to put non-rack machines to our servers rooms. So we won't be buying | + | |
- | * Yes, there are grant applications under review which include rack machines | + | |
- | Performance tests: | + | === Disk space === |
- | * [[http://www.trustedreviews.com/nvidia-geforce-gtx-1080-review-performance-benchmarks-and-conclusion-page-2| 980 vs 1080 vs Titan X (not the Titan Z we have)]] | + | All the GPU machines are at Malá Strana (not at Troja), so you should not use ''/ |
+ | - '' | ||
+ | - ''/ | ||
+ | - ''/ | ||
+ | - ''/ | ||
=== Individual acquisitions: | === Individual acquisitions: | ||
- | There is an easy way to get one high-end GPU: [[https:// | + | There is an easy way to get one high-end GPU: [[https:// |
Take care, however, to coordinate the grant applications a little, so that not too many arrive from UFAL within a short time: these grants are explicitly //not// intended to build GPU clusters, they are " | Take care, however, to coordinate the grant applications a little, so that not too many arrive from UFAL within a short time: these grants are explicitly //not// intended to build GPU clusters, they are " | ||
Line 37: | Line 39: | ||
* Ondřej Plátek - granted (2015) | * Ondřej Plátek - granted (2015) | ||
* Jan Hajič jr. - granted (early 2016) | * Jan Hajič jr. - granted (early 2016) | ||
- | * Jindra Helcl - planning to apply (fall 2016) | ||
- | ===== Installed toolkits ===== | ||
- | //This should mention where each interesting toolkit lives (on a particular machine).// | + | |
- | ==== TensorFlow | + | ===== How to use cluster ===== |
- | [[https:// | + | In this section will be explained how to use cluster properly. |
- | OP: I created [[https:// | + | ==== Set-up CUDA and CUDNN ==== |
- | === Select GPU device === | + | You can add following command into your ~/.bashrc |
- | Use variable CUDA_VISIBLE_DEVICES to constrain tensorflow to compute only on the selected one. For the use of first GPU use: | + | CUDNN_version=6.0 |
- | < | + | CUDA_version=8.0 |
+ | CUDA_DIR_OPT=/ | ||
+ | if [ -d " | ||
+ | CUDA_DIR=$CUDA_DIR_OPT | ||
+ | export CUDA_HOME=$CUDA_DIR | ||
+ | export THEANO_FLAGS=" | ||
+ | export PATH=$PATH:$CUDA_DIR/ | ||
+ | export | ||
+ | export CPATH=$CUDA_DIR/ | ||
+ | fi | ||
- | To list available devices, use: | + | ==== TensorFlow Environment ==== |
- | < | + | |
- | ===== Basic commands | + | Majority people at UFAL use TensorFlow. To start using it you need to create python virtual environment (virtualenv or use Anaconda for it). Into the environment you must place TensorFlow. The TF is either in CPU or GPU version. |
+ | |||
+ | pip install tensorflow | ||
+ | pip install tensorflow-gpu | ||
+ | |||
+ | You can use prepared environment by adding into your ~/.bashrc | ||
+ | |||
+ | export PATH=/ | ||
+ | |||
+ | And then you can activate your environment: | ||
+ | |||
+ | source activate tf1 | ||
+ | source activate tf1cpu | ||
+ | |||
+ | This environment have TensorFlow 1.0 and all necessary requirements for NeuralMonkey. | ||
+ | |||
+ | ==== Using cluster ==== | ||
+ | |||
+ | Rule number one, always use the GPU queue (never log in machine by ssh). Always use qsub or qsubmit with proper arguments. | ||
+ | |||
+ | 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, | ||
+ | |||
+ | For running experiments you must use qsub command: | ||
+ | |||
+ | qsub -q gpu.q -l gpu=1, | ||
+ | |||
+ | Cleaner way to use cluster is with / | ||
+ | |||
+ | 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 ==== | ||
lspci | lspci | ||
Line 74: | Line 115: | ||
/ | / | ||
# 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 ===== | ||
+ | |||
+ | * [[http:// | ||
+ | |||
+ | In the following table is the experiment conducted by Tom Kocmi. You can replicate experiment: / | ||
+ | |||
+ | | machine | Setup; CPU/GPU; [[https:// | ||
+ | | athena | ||
+ | | dll2 | GeForce GTX 1080; cc6.1 | | ||
+ | | titan | GeForce GTX 1080 Ti | | ||
+ | | dll1 | (2 GPU) GeForce GTX 1080; cc6.1 | | ||
+ | | dll2 | GeForce GTX 1080; cc6.1 | | ||
+ | | titan-gpu | ||
+ | | kronos-dev | Tesla K40c; cc3.5 | | ||
+ | | twister2 | ||
+ | | twister1 | ||
+ | | helena1 | ||
+ | | belzebub | ||
+ | | iridium | ||
+ | | helena7 | ||
+ | | arc | GeForce GT 630; cc3.0 | 103:42:30 | (approximated after 66 hours) | | ||
+ | | lucifer4 | ||
+ | |||
+ | |||
+ | === Second Benchmark === | ||
+ | |||
+ | The previous benchmark only compares the speed of processing units within the GPUs and do not take into account the size of memory. Therefore I have conducted another benchmark, this time for each graphic card I have increased the batch size as much as possible so the model still could fit into the GPU (the previous benchmark model had batch size 20). This way the results should be more representative of the power for each GPU. | ||
+ | |||
+ | | GPU; Cuda capability | ||
+ | | Tesla K40c; cc3.5 | 12 GB | | ||
+ | | GeForce GTX 1080 Ti; cc6.1 | 11 GB | 00:55:56 | 2300 | dll5 | | ||
+ | | GeForce GTX 1080; cc6.1 | 8 GB | 01:10:57 | 1700 | dll1 | | ||
+ | | GeForce GTX Titan Z; cc3.5 | 6 GB | 02:20:47 | 1100 | titan-gpu | | ||
+ | | Quadro K2000; cc3.0 | 2 GB | 28:15:26 | 50 | iridium | | ||
===== Links ===== | ===== Links ===== |