Differences

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

--- gpu [2016/05/02 12:33]
ufal
+++ gpu [2017/07/19 16:15]
kocmanek [Performance tests]
@@ Line 5: / Line 5: @@
 ===== Servers with GPU units =====
-| machine | GPU; [[https://en.wikipedia.org/wiki/CUDA#Supported_GPUs|Capability]] [cc]  | cores | GPU RAM    | Cuda      | Theano | TensorFlow | Comment |
+| machine                    | GPU; [[https://en.wikipedia.org/wiki/CUDA#Supported_GPUs|Capability]] [cc]  | cores | GPU RAM | Comment |
-| titan-gpu  | GeForce GTX Titan Z; cc3.5 |  2  | 6 GB each core |  V7.5.17  |   ?    |     works      |         |
+| titan                      | GeForce GTX 1080 Ti; cc6.1 | 1  | 11 GB           |  |
-| twister1   | ...has burnt         |
+| titan-gpu                  | GeForce GTX Titan Z; cc3.5 | 2  | 6 GB each core  |  |
-| twister2   | GeForce GTX 570; cc2.0 |  1  |   1 GB         |  V7.5.17  |   ?    |  no, needs cc3.0+    |         |
+| twister1; twister2; kronos | Tesla K40c; cc3.5          | 1  | 12 GB           |  |
-| kronos-dev | Tesla K40c; cc3.5?     |  1  |   12 GB        |  V6.5.12  |  0.6.0  |   ?       |         |
+| iridium                    | Quadro K2000; cc3.0        | 1  | 2 GB            |  |
-| kronos-dev | Quadro K2000; cc3.0    |  1  |  2 GB          |  as above | as above |  ?       |         |
+| victoria; arc              | GeForce GT 630; cc3.0      | 1  | 2 GB            | desktop machine |
+| athena                     | GeForce GTX 1080; cc6.1    | 1  | 8 GB            | Tom's desktop machine |
+| dll1; dll2                 | GeForce GTX 1080; cc6.1    | 8  | 8 GB each core  |  |
+| dll3; dll4; dll5           | GeForce GTX 1080 Ti; cc6.1 | 10 | 11 GB each core |  |
+not used at the moment: GeForce GTX 570 (from twister2)
+All machines have CUDA8.0 and should support both Theano and TensorFlow.
-Milan Fucik says that Troja servers can accommodate only [[http://www.czc.cz/hp-quadro-k1200-4gb/171662/produkt?ppcbee-adtext-variant=Produkt%3B+kategorie+%2B+cena%3B+Pobo%C4%8Dky&gclid=CKbKkbrWrswCFQUq0wodHDELCw|Quadro K1200 4GB]]. We should probably test Quadro K2000 there before buying any of those.
+Summary of future plans:
+  * Current Troja servers won't get any GPUs (the only option would be [[http://www.czc.cz/hp-quadro-k1200-4gb/171662/produkt?ppcbee-adtext-variant=Produkt%3B+kategorie+%2B+cena%3B+Pobo%C4%8Dky&gclid=CKbKkbrWrswCFQUq0wodHDELCw|Quadro K1200 4GB]], horribly cost-inefficient)
+  * 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 GeForce GTX 1080 (~20000CZK, out of stock now), for a non-rack machine since we most likely don't have any available.
+  * Yes, there are grant applications under review which include rack machines with GPUs, e.g. 5x2 or something like that; more will be known in 2017.
-===== Installed toolkits =====
-//This should mention where each interesting toolkit lives (on a particular machine).//
+=== Individual acquisitions: NVIDIA Academic Hardware Grants ==
-==== TensorFlow ====
+There is an easy way to get one high-end GPU: [[https://developer.nvidia.com/academic_gpu_seeding|ask NVIDIA for an Academic Hardware Grant]]. All it takes is writing a short grant application (at most ~2 hrs of work from scratch; if you have a GAUK, ~15 minutes of copy-pasting). Due to the GPU housing issues (mainly rack space and cooling), Milan F. said we should request the Tesla-line cards (2017 check with Milan about this issue). If you want to have a look at an application, feel free to ask at hajicj@ufal.mff.cuni.cz :)
-[[https://redmine.ms.mff.cuni.cz/projects/mmmt/repository/revisions/6a064187fc6959db9b77cf2d5350c5f4918a8067/entry/prepare_env.sh|This script]] installs TensorFlow 0.7.1 (and all other dependencies we need for Multimodal Translation) into `tf' and `tf-gpu' virtual environments. The GPU environment can be loaded by calling <code>source tf-gpu/bin/activate-gpu</code>.
+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 "seeding" grants meant for researchers to try out GPUs (and fall in love with them, and buy a cluster later). If you are planning to submit the hardware grant, have submitted one, or have already been awarded one, please add yourself here.
-===== Select GPU device =====
+Known NVIDIA Academic Hardware Grants:
-Use variable CUDA_VISIBLE_DEVICES to constrain tensorflow to compute only on the selected one.
+  * Ondřej Plátek - granted (2015)
+  * Jan Hajič jr. - granted (early 2016)
-===== Basic commands =====
+===== How to use cluster =====
+In this section will be explained how to use cluster properly.
+==== TensorFlow Environment ====
+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=/a/merkur3/kocmanek/ANACONDA/bin:$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,gpu_ram=2G -pty yes bash
+For running experiments you must use qsub command:
+  qsub -q gpu.q -l gpu=1,gpu_cc_min3.5=1,gpu_ram=2G WHAT_SHOULD_BE_RUN
+Cleaner way to use cluster is with /home/bojar/tools/shell/qsubmit
+  qsubmit --gpumem=2G --queue="gpu.q" WHAT_SHOULD_BE_RUN
+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
@@ Line 42: / Line 93: @@
     # dela to vubec neco uzitecneho? :-)
     # theano-* are typically located in /usr/local/bin/
+  /usr/local/cuda/samples/1_Utilities/deviceQuery/deviceQuery
+    # 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:
+  /opt/cuda/samples/1_Utilities/deviceQuery/deviceQuery | grep ^Device
+===== Performance tests =====
+* [[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)]]
+In the following table is the experiment conducted by Tom Kocmi. You can replicate experiment: /a/merkur3/kocmanek/Projects/GPUBenchmark (you will need to prepare environment of TensorFlow11 or use my ANACONDA). The benchmark uses 2GB model of seq2seq machine translation in Neural Monkey (De > EN).
+| machine | Setup; CPU/GPU; [[https://en.wikipedia.org/wiki/CUDA#Supported_GPUs|Capability]] [cc] | Walltime | Note |
+| athena     | GeForce GTX 1080; cc6.1            |    9:55:58 | Tom's desktop  |
+| dll2       | (2 GPU) GeForce GTX 1080; cc6.1    |   10:19:40 | with CUDA_VISIBLE_DEVICES=0 |
+| titan      | GeForce GTX 1080 Ti                |   10:45:11 | (new result with correct CUDA version) |
+| dll1       | (2 GPU) GeForce GTX 1080; cc6.1    |   12:34:34 | Probably only one GPU was used |
+| dll2       | (2 GPU) GeForce GTX 1080; cc6.1    |   13:01:05 | Only one GPU was used |
+| titan-gpu  | (2 GPU) GeForce GTX Titan Z; cc3.5 |   16:05:24 | Probably only one GPU was used |
+| kronos-dev | Tesla K40c; cc3.5                  |   22:41:01 |  |
+| twister2   | Tesla K40c; cc3.5                  |   22:43:10 |  |
+| twister1   | Tesla K40c; cc3.5                  |   24:19:45 |  |
+| helena1    | 16x cores CPU                      |   46:33:14 |  |
+| belzebub   | 16x cores CPU                      |   52:36:56 |  |
+| iridium    | Quadro K2000; cc3.0                |   59:47:58 |  |
+| helena7    | 8x cores CPU                       |   60:39:17 |  |
+| arc        | GeForce GT 630; cc3.0              |  103:42:30 | (approximated after 66 hours) |
+| lucifer4   | 8x cores CPU                       |  134:41:22 |  |
+=== 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       | GPU RAM |  Walltime | Batch size | Machine |
+| 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 =====

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

Institute of Formal and Applied Linguistics Wiki

Differences