Improving overall performance and energy consumption of your cluster with remote GPU virtualization

Transcription

1 Improving overall performance and energy consumption of your cluster with remote GPU virtualization Federico Silla & Carlos Reaño Technical University of Valencia Spain

2 Tutorial Agenda SESSION 1 Introduction to the remote GPU virtualization technique and frameworks Coffee break :00 SESSION 2 Talk on advanced features of remote GPU virtualization (40 minutes) Practical demonstration about how to install and use rcuda (50 minutes) 12:00-13:30 Lunch 13:30-15:00 SESSION 3 Guided exercises with rcuda in remote cluster 15:00-15:30 Coffee break 15:30-17:30 SESSION 4 Time for freely exercise with rcuda in remote cluster rcuda Tutorial. Middleware 15. December 7 th. Vancouver

3 Introduction to the remote GPU virtualization technique and frameworks Federico Silla Universidad Politécnica de Valencia Spain

4 Outline 1. Introduction to GPU computing 2. What is remote GPU virtualization? 3. Why is remote GPU virtualization needed? 4. Frameworks for remote GPU virtualization 5. Cons of remote GPU virtualization 6. Pros of remote GPU virtualization Introduction to the remote GPU virtualization technique and frameworks rcuda Tutorial. Middleware 15. December 7 th. Vancouver 2/106

5 st Outline Introduction to GPU computing rcuda Tutorial. Middleware 15. December 7 th. Vancouver 3/106

6 Current computing needs Many applications require a lot of computing resources Execution time is usually increased Applications are accelerated to get their execution time reduced GPU computing has experienced a remarkable growth in the last years rcuda Tutorial. Middleware 15. December 7 th. Vancouver 4/106

7 GPUs reduce energy and time blastp db sorted_env_nr query SequenceLength_ txt -num_threads X -gpu [t f] Dual socket E v2 Intel Xeon node with NVIDIA K20 GPU On GPU On CPU On GPU On CPU On GPU On CPU On GPU On CPU 2.36x 3.56x GPU-Blast: Accelerated version of the NCBI-BLAST (Basic Local Alignment Search Tool), a widely used bioinformatics tool rcuda Tutorial. Middleware 15. December 7 th. Vancouver 5/106

8 GPUs reduce energy and time blastp db sorted_env_nr query SequenceLength_ txt -num_threads X -gpu [t f] Dual socket E v2 Intel Xeon node with NVIDIA K20 GPU Green zone: GPUs are better than CPUs GPUs are not the magic solution for all applications Red zone: GPUs are worse than CPUs rcuda Tutorial. Middleware 15. December 7 th. Vancouver 6/106

9 Current GPU computing facilities The basic building block is a node with one or more GPUs rcuda Tutorial. Middleware 15. December 7 th. Vancouver 7/106

10 Basics of GPU computing Basic behavior of CUDA GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 8/106

11 Basics of GPU computing 1 #include <cuda.h> 2 #include <stdio.h> 3 const int N = 8; 5 // Function that will be executed in the GPU 6 global void my_gpu_function (int *a, int *b) 7 {b[threadidx.x] = a[threadidx.x ] * 2;} 9 int main ( ) 10 { 11 int a[n] = {0, 1, 2, 3, 4, 5, 6, 7 }; 12 int *ad, *bd; 13 const int isize = N * sizeof(int); 14 // Perform some computations in the CPU 15 CPU code CPU code 17 // Allocate GPU memory 18 cudamalloc ((void**)&ad, isize); 19 cudamalloc ((void**)&bd, isize); 27 // Copy results from GPU memory 28 cudamemcpy(b, bd, isize, cudamemcpydevicetohost); 30 // Free GPU memory 31 cudafree(ad); 32 cudafree(bd); 33 return 0; 34 } 21 // Copy data to GPU memory 22 cudamemcpy(ad, a, isize, cudamemcpyhosttodevice); 24 // Execute function in the GPU 25 my_gpu_function<<<1, N>>>(ad, bd); rcuda Tutorial. Middleware 15. December 7 th. Vancouver 9/106

12 Heterogeneous clusters From the programming point of view: A set of nodes, each one with: one or more CPUs (with several cores per CPU) one or more GPUs (typically between 1 and 4) An interconnection network rcuda Tutorial. Middleware 15. December 7 th. Vancouver 10/106

13 Characteristics of GPU-based clusters A GPU-enabled cluster is a set of independent self-contained nodes. The cluster follows the shared-nothing approach: Nothing is directly shared among nodes (MPI required for aggregating computing resources within the cluster, included GPUs) GPUs can only be used within the node they are attached to node 1 node 2 node 3 node n GPU GPU GPU GPU PCIe CPU CPU PCIe CPU CPU PCIe CPU CPU PCIe CPU CPU Network Network Network Network Interconnection Network rcuda Tutorial. Middleware 15. December 7 th. Vancouver 11/106

14 Outline ndimproving overall performance & energy consumption of your cluster with remote GPU virtualization What is remote GPU virtualization? rcuda Tutorial. Middleware 15. December 7 th. Vancouver 12/106

15 It has to do with GPUs, obviously! rcuda Tutorial. Middleware 15. December 7 th. Vancouver 13/106

16 Remote GPU virtualization GPU With CUDA (local) No GPU A software technology that enables a more flexible use of GPUs in computing facilities rcuda Tutorial. Middleware 15. December 7 th. Vancouver 14/106

17 Same source code for using virtual GPUs 1 #include <cuda.h> 2 #include <stdio.h> 3 const int N = 8; 5 // Function that will be executed in the GPU 6 global void my_gpu_function (int *a, int *b) 7 {b[threadidx.x] = a[threadidx.x ] * 2;} 9 int main ( ) 10 { 11 int a[n] = {0, 1, 2, 3, 4, 5, 6, 7 }; 12 int *ad, *bd; 13 const int isize = N * sizeof(int); 14 // Perform some computations in the CPU 15 CPU code CPU code 17 // Allocate GPU memory 18 cudamalloc ((void**)&ad, isize); 19 cudamalloc ((void**)&bd, isize); 21 // Copy data to GPU memory 22 cudamemcpy(ad, a, isize, cudamemcpyhosttodevice); 24 // Execute function in the GPU 25 my_gpu_function<<<1, N>>>(ad, bd); Application source code does not change. The change is linking against the remote GPU virtualization libraries instead of using the original CUDA libraries 27 // Copy results from GPU memory 28 cudamemcpy(b, bd, isize, cudamemcpydevicetohost); 30 // Free GPU memory 31 cudafree(ad); 32 cudafree(bd); 33 return 0; 34 } rcuda Tutorial. Middleware 15. December 7 th. Vancouver 15/106

18 Basics of remote GPU virtualization rcuda Tutorial. Middleware 15. December 7 th. Vancouver 16/106

19 Basics of remote GPU virtualization rcuda Tutorial. Middleware 15. December 7 th. Vancouver 17/106

20 Remote GPU virtualization envision Remote GPU virtualization allows a new vision of a GPU deployment, moving from the usual cluster configuration: node 1 node 2 node 3 node n PCIe GPU CPU CPU GPU GPU GPU PCIe CPU CPU PCIe CPU CPU Network Network Network Network PCIe CPU CPU Physical configuration Interconnection Network GPU GPU GPU GPU node 1 Logical connections node 2 node 3 node n Logical configuration PCIe CPU CPU Network PCIe CPU CPU Network PCIe CPU CPU Network PCIe CPU CPU Network Interconnection Network rcuda Tutorial. Middleware 15. December 7 th. Vancouver 18/106

21 Remote GPU virtualization envision Real local GPUs node 1 node 2 node 3 node n GPU GPU GPU GPU PCIe CPU PCIe CPU PCIe CPU PCIe CPU CPU CPU CPU CPU Without GPU virtualization Network Network Network Network Interconnection Network With GPU virtualization Virtualized remote GPUs GPU n GPU 3 GPU 2 GPU GPU GPU GPU GPU GPU GPU GPU GPU GPU GPU GPU GPU 1 GPU GPU GPU GPU GPU virtualization allows all nodes to share all GPUs PCIe CPU CPU Network PCIe CPU CPU PCIe CPU CPU Network Network Interconnection Network PCIe CPU CPU Network rcuda Tutorial. Middleware 15. December 7 th. Vancouver 19/106

22 rd Outline Why is remote GPU virtualization needed? rcuda Tutorial. Middleware 15. December 7 th. Vancouver 20/106

23 Outline Which is the problem with GPU-enabled clusters? rcuda Tutorial. Middleware 15. December 7 th. Vancouver 21/106

24 The problem is the cluster architecture A GPU-enabled cluster is a set of independent self-contained nodes. The cluster follows the shared-nothing approach: Nothing is directly shared among nodes (MPI required for aggregating computing resources within the cluster, included GPUs) GPUs can only be used within the node they are attached to node 1 node 2 node 3 node n GPU GPU GPU GPU PCIe CPU CPU PCIe CPU CPU PCIe CPU CPU PCIe CPU CPU Network Network Network Network Interconnection Network rcuda Tutorial. Middleware 15. December 7 th. Vancouver 22/106

25 First concern with accelerated clusters Non-accelerated applications keep GPUs idle in the nodes where they use all the cores Hybrid MPI shared-memory non-accelerated applications usually span to all the cores in a node (across n nodes) A CPU-only application spreading over these nodes will make their GPUs unavailable for accelerated applications node 1 node 2 node 3 node n GPU GPU GPU GPU PCIe CPU PCIe CPU PCIe CPU PCIe CPU CPU CPU CPU CPU Network Network Network Network Interconnection Network rcuda Tutorial. Middleware 15. December 7 th. Vancouver 23/106

26 Money leakage in current clusters? Idle Power (Watts) For some workloads, GPUs may be idle for significant periods of time: Initial acquisition costs not amortized Space: GPUs reduce CPU density Energy: idle GPUs keep consuming power 4 GPUs node 1 GPU node 25% 1 GPU node: Two E v2 sockets and 32GB DDR3. One Tesla K20 GPU 4 GPU node: Two E v2 sockets and 128GB DDR3. Four Tesla K20 GPUs Time (s) rcuda Tutorial. Middleware 15. December 7 th. Vancouver 24/106

27 First concern with accelerated clusters (II) Accelerated applications keep CPUs idle in the nodes where they execute Hybrid MPI shared-memory non-accelerated applications usually span to all the cores in a node (across n nodes) An accelerated application using just one CPU core may avoid other jobs to be dispatched to this node node 1 node 2 node 3 node n GPU GPU GPU GPU PCIe CPU PCIe CPU PCIe CPU PCIe CPU CPU CPU CPU CPU Network Network Network Network Interconnection Network rcuda Tutorial. Middleware 15. December 7 th. Vancouver 25/106

28 First concern with accelerated clusters (II) Accelerated applications keep CPUs idle in the nodes where they execute Hybrid MPI shared-memory non-accelerated applications usually span to all the cores in a node (across n nodes) An accelerated MPI application using just one CPU core per node may keep part of the cluster busy node 1 node 2 node 3 node n GPU GPU GPU GPU PCIe CPU PCIe CPU PCIe CPU PCIe CPU CPU CPU CPU CPU Network Network Network Network Interconnection Network rcuda Tutorial. Middleware 15. December 7 th. Vancouver 26/106

29 Second concern with accelerated clusters Non-MPI multi-gpu applications cannot make use of the tremendous GPU resources available across the cluster (even if those GPU resources are idle) Non-MPI multi-gpu application All these GPUs cannot be used by the multi-gpu application being executed node 1 node 2 node 3 node n GPU GPU GPU GPU PCIe CPU PCIe CPU PCIe CPU PCIe CPU CPU CPU CPU CPU Network Network Network Network Interconnection Network rcuda Tutorial. Middleware 15. December 7 th. Vancouver 27/106

30 One more concern with accelerated clusters Do applications completely squeeze the GPUs available in the cluster? When a GPU is assigned to an application, computational resources inside the GPU may not be fully used Application presenting low level of parallelism CPU code being executed (GPU assigned GPU working) GPU-core stall due to lack of data etc node 1 node 2 node 3 node n GPU GPU GPU GPU PCIe CPU PCIe CPU PCIe CPU PCIe CPU CPU CPU CPU CPU Network Network Network Network Interconnection Network rcuda Tutorial. Middleware 15. December 7 th. Vancouver 28/106

31 GPU usage of GPU-Blast GPU assigned but not used GPU assigned but not used rcuda Tutorial. Middleware 15. December 7 th. Vancouver 29/106

32 GPU usage of CUDA-MEME GPU utilization is far away from maximum rcuda Tutorial. Middleware 15. December 7 th. Vancouver 30/106

33 GPU usage of LAMMPS GPU assigned but not used rcuda Tutorial. Middleware 15. December 7 th. Vancouver 31/106

34 GPU usage of CUDASW GPU assigned but not used GPU assigned but not used rcuda Tutorial. Middleware 15. December 7 th. Vancouver 32/106

35 GPU allocation vs GPU utilization GPUs assigned but not used rcuda Tutorial. Middleware 15. December 7 th. Vancouver 33/106

36 Sharing a GPU among jobs: GPU-Blast One instance required about 51 seconds Two concurrent instances of GPU-Blast rcuda Tutorial. Middleware 15. December 7 th. Vancouver 34/106

37 Sharing a GPU among jobs: GPU-Blast First instance Two concurrent instances of GPU-Blast rcuda Tutorial. Middleware 15. December 7 th. Vancouver 35/106

38 Sharing a GPU among jobs: GPU-Blast Second instance First instance Two concurrent instances of GPU-Blast rcuda Tutorial. Middleware 15. December 7 th. Vancouver 36/106

39 Sharing a GPU among jobs: GPU-Blast One instance required about 51 seconds Four concurrent instances of GPU-Blast rcuda Tutorial. Middleware 15. December 7 th. Vancouver 37/106

40 Sharing a GPU among jobs: GPU-Blast Several GPU-Blast instances concurrently executed on the same GPU. Each instance requires about 1.5 GB of GPU memory Execution time missmatch with previous slides due to the use of different input data sets!! rcuda Tutorial. Middleware 15. December 7 th. Vancouver 38/106

41 Sharing a GPU among jobs K20 GPU LAMMPS: 876 MB mcuda-meme: 151 MB BarraCUDA: 3319 MB MUMmerGPU: 2104 MB GPU-LIBSVM: 145 MB rcuda Tutorial. Middleware 15. December 7 th. Vancouver 39/106

42 Back to first concern Accelerated applications keep CPUs idle in the nodes where they execute Hybrid MPI shared-memory non-accelerated applications usually span to all the cores in a node (across n nodes) An accelerated MPI application using just one CPU core per node may keep part of the cluster busy node 1 node 2 node 3 node n GPU GPU GPU GPU PCIe CPU PCIe CPU PCIe CPU PCIe CPU CPU CPU CPU CPU Network Network Network Network Interconnection Network rcuda Tutorial. Middleware 15. December 7 th. Vancouver 40/106

43 Back to first concern Accelerated applications keep CPUs idle in the nodes where they execute Hybrid MPI shared-memory non-accelerated applications usually span to all the cores in a node (across n nodes) node 1 GPU node 2 node 3 GPU An accelerated MPI application using just one CPU core per node may keep part of the cluster busy GPU Idle CPU cores in nodes executing accelerated node n applications could GPU be used for other GPU applications PCIe CPU PCIe CPU PCIe CPU PCIe CPU CPU CPU CPU CPU Network Network Network Network Interconnection Network rcuda Tutorial. Middleware 15. December 7 th. Vancouver 41/106

44 Performance in GPU clusters is lost In summary There are scenarios where GPUs are available but cannot be used Also, CPU cores are available but cannot be used Accelerated applications do not make use of 100% of GPU resources In conclusion GPU and CPU cycles are lost, thus reducing cluster performance rcuda Tutorial. Middleware 15. December 7 th. Vancouver 42/106

45 We need something more in the cluster The current model for using GPUs is too rigid What is missing is some flexibility for using the GPUs in the cluster rcuda Tutorial. Middleware 15. December 7 th. Vancouver 43/106

46 We need something more in the cluster The current model for using GPUs is too rigid What is missing is some flexibility for using the GPUs in the cluster A way of seamlessly sharing GPUs across nodes in the cluster (remote GPU virtualization) rcuda Tutorial. Middleware 15. December 7 th. Vancouver 44/106

47 Remote GPU virtualization node 1 node 2 node 3 node n PCIe GPU CPU CPU GPU GPU GPU PCIe CPU CPU PCIe CPU CPU Network Network Network Network PCIe CPU CPU Physical configuration Interconnection Network GPU GPU GPU GPU node 1 Logical connections node 2 node 3 node n Logical configuration PCIe CPU CPU PCIe CPU CPU PCIe CPU CPU Network Network Network Network PCIe CPU CPU Interconnection Network rcuda Tutorial. Middleware 15. December 7 th. Vancouver 45/106

48 Increasing flexibility: one step further Once GPUs are shared, their amount can be reduced to match the actual workload This would increase GPU utilization, also lowering power consumption, at the same time that initial acquisition costs are reduced rcuda Tutorial. Middleware 15. December 7 th. Vancouver 46/106

49 Sharing GPUs among applications Real local GPUs node 1 node 2 node 3 node n GPU GPU GPU GPU PCIe CPU PCIe CPU PCIe CPU PCIe CPU CPU CPU CPU CPU Without GPU virtualization Network Network Network Network Interconnection Network With GPU virtualization Virtualized remote GPUs GPU n GPU 3 GPU 2 GPU GPU GPU GPU GPU GPU GPU GPU GPU GPU GPU GPU GPU 1 GPU GPU GPU GPU GPU virtualization allows all nodes to share all GPUs PCIe CPU CPU Network PCIe CPU CPU PCIe CPU CPU Network Network Interconnection Network PCIe CPU CPU Network rcuda Tutorial. Middleware 15. December 7 th. Vancouver 47/106

50 What is needed for increased flexibility? In summary this new cluster configuration requires: A way of seamlessly sharing GPUs across nodes in the cluster (remote GPU virtualization) Enhanced job schedulers that take into account the new virtual GPUs rcuda Tutorial. Middleware 15. December 7 th. Vancouver 48/106

51 th Outline Frameworks for remote GPU virtualization rcuda Tutorial. Middleware 15. December 7 th. Vancouver 49/106

52 Remote GPU virtualization frameworks Several efforts have been made to implement remote GPU virtualization during the last years: rcuda (CUDA 7.0) GVirtuS (CUDA 3.2) DS-CUDA (CUDA 4.1) vcuda (CUDA 1.1) GViM (CUDA 1.1) GridCUDA (CUDA 2.3) V-GPU (CUDA 4.0) Publicly available NOT publicly available rcuda is a development by Technical University of Valencia rcuda Tutorial. Middleware 15. December 7 th. Vancouver 50/106

53 Remote GPU virtualization frameworks FDR InfiniBand + K20!! H2D pageable D2H pageable H2D pinned D2H pinned rcuda Tutorial. Middleware 15. December 7 th. Vancouver 51/106

54 rcuda uses optimized transfers rcuda features optimized data transfers: Pipelined transfers to improve performance Preallocated pinned memory buffers Optimal pipeline block size rcuda Tutorial. Middleware 15. December 7 th. Vancouver 52/106

55 Moving data WITHOUT a pipeline Pageable memory area to be copied to remote GPU Destination memory area in the remote GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 53/106

56 Moving data WITHOUT a pipeline Pageable memory area to be copied to remote GPU Memory area copied to network buffers for RDMA Destination memory area in the remote GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 54/106

57 Moving data WITHOUT a pipeline Pageable memory area to be copied to remote GPU Memory area copied to network buffers for RDMA Memory area arrives at network buffers at remote server Destination memory area in the remote GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 55/106

58 Moving data WITHOUT a pipeline Pageable memory area to be copied to remote GPU Memory area copied to network buffers for RDMA Memory area arrives at network buffers at remote server Destination memory area in the remote GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 56/106

59 Moving data WITHOUT a pipeline Main memory to network buffers Network from client to remote server Network buffers to GPU memory Transmission time without pipeline rcuda Tutorial. Middleware 15. December 7 th. Vancouver 57/106

60 Moving data WITH a pipeline Pageable memory area to be copied to remote GPU Destination memory area in the remote GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 58/106

61 Moving data WITH a pipeline Pageable memory area to be copied to remote GPU Memory area is split into chunks (pipeline blocks) Destination memory area in the remote GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 59/106

62 Moving data WITH a pipeline Pageable memory area to be copied to remote GPU Only two small network buffers at source and destination are required Destination memory area in the remote GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 60/106

63 Moving data WITH a pipeline Pageable memory area to be copied to remote GPU Transmission starts by moving forward the first block Destination memory area in the remote GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 61/106

64 Moving data WITH a pipeline Pageable memory area to be copied to remote GPU 2 pipeline stages concurrently move data forward Destination memory area in the remote GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 62/106

65 Moving data WITH a pipeline Pageable memory area to be copied to remote GPU The three stages of the pipeline are concurrently transferring data forward Destination memory area in the remote GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 63/106

66 Moving data WITH a pipeline Pageable memory area to be copied to remote GPU Destination memory area in the remote GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 64/106

67 Moving data WITH a pipeline Pageable memory area to be copied to remote GPU Destination memory area in the remote GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 65/106

68 Moving data WITH a pipeline Pageable memory area to be copied to remote GPU Destination memory area in the remote GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 66/106

69 Moving data WITH a pipeline Pageable memory area to be copied to remote GPU Destination memory area in the remote GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 67/106

70 Moving data without a pipeline Main memory to network buffers Network from client to remote server Network buffers to GPU memory Management of data transfer is much more complex Transmission time with pipeline Improvement Transmission time without pipeline Without pipeline rcuda Tutorial. Middleware 15. December 7 th. Vancouver 68/106

71 Bandwidth (MB/s) Basic performance analysis Bandwidth (MB/s) Pipeline block size for InfiniBand Connect-IB It was 2MB with IB QDR and 1MB with FDR X3 1 port 2 ports Copy Size (MB) H2D pinned Copy Size (MB) NVIDIA Tesla K40; Mellanox Connect-IB + SX6036 Mellanox switch rcuda Tutorial. Middleware 15. December 7 th. Vancouver 69/106

72 Communication between client and server rcuda uses a proprietary communication protocol Example: 1) initialization 2) memory allocation on the remote GPU 3) CPU to GPU memory transfer of the input data 4) kernel execution 5) GPU to CPU memory transfer of the results 6) GPU memory release 7) communication channel closing and server process finalization rcuda Tutorial. Middleware 15. December 7 th. Vancouver 70/106

73 How applications use remote GPUs Environment variables are properly initialized in the client side and used by the rcuda client (transparently to the application) Server name/ip address : GPU Amount of GPUs assigned to application rcuda Tutorial. Middleware 15. December 7 th. Vancouver 71/106

74 th Outline Cons of remote GPU virtualization rcuda Tutorial. Middleware 15. December 7 th. Vancouver 72/106

75 Problem with remote GPU virtualization The main drawback of remote GPU virtualization is the reduced bandwidth to the remote GPU No GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 73/106

76 Using InfiniBand networks rcuda Tutorial. Middleware 15. December 7 th. Vancouver 74/106

77 Performance of rcuda CUDASW++ Bioinformatics software for Smith-Waterman protein database searches rcuda Overhead (%) FDR Overhead QDR Overhead GbE Overhead CUDA rcuda FDR rcuda QDR rcuda GbE Sequence Length Execution Time (s) Dual socket E v2 Intel Xeon node with NVIDIA K20 GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 75/106

78 Performance of rcuda GPU-Blast Accelerated version of the NCBI-BLAST (Basic Local Alignment Search Tool), a widely used bioinformatics tool rcuda Overhead (%) FDR Overhead QDR Overhead GbE Overhead CUDA rcuda FDR rcuda QDR rcuda GbE Sequence Length Execution Time (s) Dual socket E v2 Intel Xeon node with NVIDIA K20 GPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 76/106

79 Initial transfers of rcuda with InfiniBand H2D pageable D2H pageable rcuda FDR Orig rcuda EDR Orig rcuda FDR Opt rcuda EDR Opt H2D pinned D2H pinned rcuda Tutorial. Middleware 15. December 7 th. Vancouver 77/106

80 Improving communications within rcuda Several optimizations applied to rcuda: At the InfiniBand level: Optimization intended for short transfers Optimization intended for long transfers At the rcuda level: The internal pipeline has been redesigned rcuda Tutorial. Middleware 15. December 7 th. Vancouver 78/106

81 Using InfiniBand networks Applications use InfiniBand by creating queue pairs (QPs): QPs do not store data but work requests (WRs) Work requests are descriptors of the transfer operation to be done Applications can associate several QPs to the same network adapter The more QPs, the higher the complexity of keeping them synchronized rcuda Tutorial. Middleware 15. December 7 th. Vancouver 79/106

82 Improving communications within rcuda Optimization for short transfers: increase the capacity of the send/receive queues (i.e., number of work requests that can be allocated) InfiniBand RDMA write bandwidth test rcuda Tutorial. Middleware 15. December 7 th. Vancouver 80/106

83 Improving communications within rcuda Optimization for long transfers: increase the number of QPs used for a single transfer InfiniBand RDMA write bandwidth test rcuda Tutorial. Middleware 15. December 7 th. Vancouver 81/106

84 Optimized transfers within rcuda H2D pageable D2H pageable rcuda FDR Orig rcuda EDR Orig rcuda FDR Opt rcuda EDR Opt Almost 100% of available BW H2D pinned Almost 100% of available BW D2H pinned rcuda Tutorial. Middleware 15. December 7 th. Vancouver 82/106

85 rcuda optimizations on applications Several applications executed with CUDA and rcuda: K20 GPU and FDR InfiniBand K40 GPU and EDR InfiniBand Lower is better rcuda Tutorial. Middleware 15. December 7 th. Vancouver 83/106

86 rcuda optimizations on applications Two are the reasons for the better performance of rcuda: 1. Higher bandwidth for pageable memory 2. Network polling interval to check for work completions: CUDA polls PCIe whereas rcuda polls InfiniBand network adapter Clock sample from NVIDIA SDK rcuda Tutorial. Middleware 15. December 7 th. Vancouver 84/106

87 Rodinia performance with rcuda InfiniBand EDR + K40!! Short execution time Medium execution time Long execution time rcuda Tutorial. Middleware 15. December 7 th. Vancouver 85/106

88 Rodinia performance with rcuda InfiniBand EDR + K40!! rcuda Tutorial. Middleware 15. December 7 th. Vancouver 86/106

89 LAMMPS performance with rcuda InfiniBand EDR + K40 InfiniBand FDR + K20 rcuda Tutorial. Middleware 15. December 7 th. Vancouver 87/106

90 th Outline Pros of remote GPU virtualization rcuda Tutorial. Middleware 15. December 7 th. Vancouver 88/106

91 1: more GPUs for a single application GPU virtualization is useful for multi-gpu applications node 1 node 2 node 3 node n Only the GPUs in the node can be provided to the application PCIe GPU CPU CPU GPU GPU GPU PCIe CPU CPU PCIe CPU CPU Network Network Network Network PCIe CPU CPU Without GPU virtualization Interconnection Network With GPU virtualization Many GPUs in the cluster can be provided to the application PCIe GPU GPU GPU GPU Logical connections node 1 node 2 node 3 node n CPU CPU PCIe CPU CPU PCIe CPU CPU Network Network Network Network Interconnection Network PCIe CPU CPU rcuda Tutorial. Middleware 15. December 7 th. Vancouver 89/106

92 1: more GPUs for a single application 64 GPUs! rcuda Tutorial. Middleware 15. December 7 th. Vancouver 90/106

93 1: more GPUs for a single application MonteCarlo Multi-GPU (from NVIDIA samples) FDR InfiniBand + NVIDIA Tesla K20 Higher is better Lower is better rcuda Tutorial. Middleware 15. December 7 th. Vancouver 91/106

94 2: busy CPU cores do not block GPUs node 1 node 2 node 3 node n GPU GPU GPU GPU PCIe CPU PCIe CPU PCIe CPU PCIe CPU Physical CPU Network CPU Network CPU Network CPU Network configuration Interconnection Network GPU GPU GPU GPU Logical connections PCIe node 1 CPU CPU PCIe node 2 node 3 CPU CPU PCIe CPU CPU PCIe node n CPU CPU Logical configuration Network Network Network Network Interconnection Network rcuda Tutorial. Middleware 15. December 7 th. Vancouver 92/106

95 3: easier cluster upgrade A cluster without GPUs needs to be upgraded to use GPUs No GPU GPUs require large power supplies Are power supplies already installed in the nodes large enough? GPUs require large amounts of space Does current form factor of the nodes allow to install GPUs? The answer to both questions should be NO rcuda Tutorial. Middleware 15. December 7 th. Vancouver 93/106

96 3: easier cluster upgrade Approach 1: augment the cluster with some CUDA GPUenabled nodes only those GPU-enabled nodes can execute accelerated applications No GPU GPU-enabled rcuda Tutorial. Middleware 15. December 7 th. Vancouver 94/106

97 3: easier cluster upgrade Approach 2: augment the cluster with some rcuda servers all nodes can execute accelerated applications GPU-enabled rcuda Tutorial. Middleware 15. December 7 th. Vancouver 95/106

98 3: easier cluster upgrade Dual socket E5-2620v2 Intel Xeon + 32GB + K20 GPU FDR InfiniBand based cluster 15 nodes without GPU + 1 node with 4 GPUs node with the Slurm scheduler rcuda Tutorial. Middleware 15. December 7 th. Vancouver 96/106

99 Non-GPU 3: easier cluster upgrade Applications used for tests: GPU-Blast (21 seconds; 1 GPU; 1599 MB) LAMMPS short (90 seconds; 1 GPU; 2633 MB) LAMMPS long 2p (149 seconds; 2 GPUs; 3950 MB) LAMMPS long 4p (71 seconds; 4 GPUs; 2385 MB) mcuda-meme short (510 seconds; 1 GPU; 151 MB) mcuda-meme long 2p (1182 seconds; 2 GPUs; 152 MB) mcuda-meme long 4p (631 seconds; 4 GPUs; 152 MB) BarraCUDA (10 minutes; 1 GPU; 3319 MB) GPU-LIBSVM (5 minutes; 1GPU; 145 MB) MUMmerGPU (5 minutes; 1GPU; 2804 MB) GROMACS (167 seconds) NAMD (11 minutes) rcuda Tutorial. Middleware 15. December 7 th. Vancouver 97/106

100 3: easier cluster upgrade rcuda Tutorial. Middleware 15. December 7 th. Vancouver 98/106

101 3: easier cluster upgrade -68% -60% +131% +119% -63% -56% rcuda Tutorial. Middleware 15. December 7 th. Vancouver 99/106

102 4: GPU consolidation Concentrate GPUs into dedicated GPU boxes (with a low-power CPU) Allow GPU task migration rcuda Tutorial. Middleware 15. December 7 th. Vancouver 100/106

103 4: GPU consolidation Box A has 4 GPUs but only one is busy Box B has 8 GPUs but only two are busy 1. Move jobs from Box B to Box A and switch off Box B 2. Migration should be transparent to applications (decided by the global scheduler) Box B Box A TRUE GREEN GPU COMPUTING rcuda Tutorial. Middleware 15. December 7 th. Vancouver 101/106

104 4: GPU consolidation: one step beyond Job granularity instead of GPU granularity rcuda Tutorial. Middleware 15. December 7 th. Vancouver 102/106

105 Additional benefits 5. Easier access from the inside of virtual machines to GPUs 6. Increased performance at the cluster level Cluster throughput (jobs/hour) is doubled More details in the second part of the tutorial rcuda Tutorial. Middleware 15. December 7 th. Vancouver 103/106

106 Get a free copy of rcuda at More than 650 requests world rcuda is a development by Technical University of Valencia rcuda Tutorial. Middleware 15. December 7 th. Vancouver 104/106

107 Get a free copy of rcuda at More than 650 requests world Carlos Reaño Javier Prades Sergio Iserte rcuda is a development by Technical University of Valencia rcuda Tutorial. Middleware 15. December 7 th. Vancouver 105/106

108 Thanks! Questions? rcuda is a development by Technical University of Valencia rcuda Tutorial. Middleware 15. December 7 th. Vancouver 106/106

109 Advanced features of rcuda Federico Silla Universidad Politécnica de Valencia

110 Additional benefits 5. Easier access from the inside of virtual machines to GPUs 6. Increased performance at the cluster level Cluster throughput (jobs/hour) is doubled More details in the second part of the tutorial rcuda Tutorial. Middleware 15. December 7 th. Vancouver 2/33

111 5: virtual machines can easily access GPUs How to access the GPU in the native domain from the inside of the virtual machines? rcuda Tutorial. Middleware 15. December 7 th. Vancouver 3/33

112 5: virtual machines can easily access GPUs The GPU is assigned by using PCI passthrough exclusively to a single virtual machine Concurrent usage of the GPU is not possible rcuda Tutorial. Middleware 15. December 7 th. Vancouver 4/33

113 How to attach an InfiniBand card to a VM SR-IOV Physical Function; PF Virtual IB card copies (Virtual Functions; VFs) PCI passthrough is used to assign an InfiniBand card (either real or virtual) to a given VM The InfiniBand card manages the several virtual copies rcuda Tutorial. Middleware 15. December 7 th. Vancouver 5/33

114 5: virtual machines can easily access GPUs High performance network available Low performance network available KVM rcuda Tutorial. Middleware 15. December 7 th. Vancouver 6/33

115 5: virtual machines can easily access GPUs High performance network available Low performance network available Xen rcuda Tutorial. Middleware 15. December 7 th. Vancouver 7/33

116 FDR InfiniBand + K20!! Application performance with KVM LAMMPS CUDA-MEME CUDASW++ GPU-BLAST rcuda Tutorial. Middleware 15. December 7 th. Vancouver 8/33

117 FDR InfiniBand + K20!! Application performance with Xen LAMMPS CUDA-MEME CUDASW++ GPU-BLAST rcuda Tutorial. Middleware 15. December 7 th. Vancouver 9/33

118 Overhead of rcuda within VMs 1.6% 2.5% 0.5% KVM 0.07% 6.1% Xen FDR InfiniBand + K20!! 2.9% 0.7% 2.3% rcuda Tutorial. Middleware 15. December 7 th. Vancouver 10/33

119 5: increased performance for clusters rcuda Tutorial. Middleware 15. December 7 th. Vancouver 11/33

120 rcuda at cluster level Slurm GPUs can be shared among jobs running in remote clients Job scheduler required for coordination Slurm was selected App 1 App 2 App 3 App 4 App 5 App 6 App 7 App 8 App 9 rcuda Tutorial. Middleware 15. December 7 th. Vancouver 12/33

121 The basic idea about SLURM rcuda Tutorial. Middleware 15. December 7 th. Vancouver 13/33

122 The basic idea about SLURM + rcuda GPUs are decoupled from nodes All jobs are executed in less time rcuda Tutorial. Middleware 15. December 7 th. Vancouver 14/33

123 Sharing remote GPUs among jobs GPU 0 is scheduled to be shared among jobs GPUs are decoupled from nodes All jobs are executed even in less time rcuda Tutorial. Middleware 15. December 7 th. Vancouver 15/33

124 GPU memory is the limit GPU memory App 1 App 2 App 5 App 3 App 4 App 6 rcuda Tutorial. Middleware 15. December 7 th. Vancouver 16/33

125 GPU memory is the limit GPU memory Does app 7 fit into the GPU? App 1 App 2 App 5 App 3 App 4 App 6 rcuda Tutorial. Middleware 15. December 7 th. Vancouver 17/33

126 Integrating rcuda with SLURM SLURM does not know about virtualized GPUs SLURM must be enhanced in order to manage the new virtualized GPUs A new resource has been added: rgpu gres.conf Name = rgpu File =/dev/nvidia0 Cuda=3.5 Mem=4726 M [ Name =gpu File =/dev/nvidia0 ] slurm.conf SelectType = select / cons_rgpu SelectTypeParameters = CR_CORE GresTypes = rgpu [,gpu] NodeName = node1 NodeHostname = node1 CPUs=12 Sockets=2 CoresPerSocket=6 ThreadsPerCore=1 RealMemory=32072 Gres = rgpu :1[, gpu :1] New submission options: --rcuda-mode=(shared excl) --gres=rgpu(:x(:y)?(:z)?)? X = [1-9]+[0-9]* Y = [1-9]+[0-9]*[ kkmmgg] Z = [1-9]\.[0-9](cc CC) rcuda Tutorial. Middleware 15. December 7 th. Vancouver 18/33

127 Non-GPU Ongoing work: studying rcuda+slurm Applications used for tests: GPU-Blast (21 seconds; 1 GPU; 1599 MB) LAMMPS (15 seconds; 4 GPUs; 876 MB) mcuda-meme (165 seconds; 4 GPUs; 151 MB) GROMACS (167 seconds) NAMD (11 minutes) BarraCUDA (10 minutes; 1 GPU; 3319 MB) GPU-LIBSVM (5 minutes; 1GPU; 145 MB) MUMmerGPU (5 minutes; 1GPU; 2104 MB) Set 1 Set 2 Short execution time Long execution time Three workloads: Set 1 Set 2 Set 1 + Set 2 Three workload sizes: Small (100 jobs) Medium (200 jobs) Large (400 jobs) rcuda Tutorial. Middleware 15. December 7 th. Vancouver 19/33

128 Ongoing work: studying rcuda+slurm rcuda Tutorial. Middleware 15. December 7 th. Vancouver 20/33

129 Test bench for studying rcuda+slurm Dual socket E5-2620v2 Intel Xeon + 32GB + K20 GPU FDR InfiniBand based cluster 4 GPU nodes node with the Slurm scheduler 8 GPU nodes node with the Slurm scheduler 16 GPU nodes node with the Slurm scheduler rcuda Tutorial. Middleware 15. December 7 th. Vancouver 21/33

130 Results for 16-node cluster Lower is better Workload size is 400 jobs Lower is better Higher is better rcuda Tutorial. Middleware 15. December 7 th. Vancouver 22/33

131 Results for 16-node cluster rcuda Tutorial. Middleware 15. December 7 th. Vancouver 23/33

132 Results for 16-node cluster rcuda Tutorial. Middleware 15. December 7 th. Vancouver 24/33

133 Results for 16-node cluster Lower is better Workload size is 400 jobs Lower is better Higher is better rcuda Tutorial. Middleware 15. December 7 th. Vancouver 25/33

134 non-homogeneous cluster Dual socket E5-2620v2 Intel Xeon + 32GB + K20 GPU FDR InfiniBand based cluster 15 nodes with 1 GPU + 1 node with 4 GPUs node with the Slurm scheduler rcuda Tutorial. Middleware 15. December 7 th. Vancouver 26/33

135 non-homogeneous cluster Lower is better Workload size is 400 jobs Lower is better Higher is better rcuda Tutorial. Middleware 15. December 7 th. Vancouver 27/33

136 non-homogeneous cluster rcuda Tutorial. Middleware 15. December 7 th. Vancouver 28/33

137 Outline in summary rcuda Tutorial. Middleware 15. December 7 th. Vancouver 29/33

138 Pros and cons of rcuda Cons: 1.Reduced bandwidth to remote GPU (really a concern??) Pros: 1.Many GPUs for a single application 2.Concurrent GPU access to virtual machines 3.Increased cluster throughput 4.Similar performance with smaller investment 5.Easier (cheaper) cluster upgrade 6.Migration of GPU jobs 7.Reduced energy consumption 8.Increased GPU utilization rcuda Tutorial. Middleware 15. December 7 th. Vancouver 30/33

139 rcuda is the enabling technology for High Throughput Computing Sharing remote GPUs makes applications to execute slower BUT more throughput (jobs/time) is achieved Datacenter administrators can choose between HPC and HTC Green Computing GPU migration and application migration allow to devote just the required computing resources to the current load More flexible system upgrades GPU and CPU updates become independent from each other. Adding GPU boxes to non GPUenabled clusters is possible rcuda Tutorial. Middleware 15. December 7 th. Vancouver 31/33

140 Get a free copy of rcuda at More than 650 requests world rcuda is a development by Technical University of Valencia rcuda Tutorial. Middleware 15. December 7 th. Vancouver 32/33

141 Thanks! Questions? rcuda is a development by Technical University of Valencia rcuda Tutorial. Middleware 15. December 7 th. Vancouver 33/33

142 Hands-on Session (Part I) Carlos Reaño Technical University of Valencia Spain

143 Outline What is rcuda? Installing and using rcuda rcuda over HPC networks InfiniBand How taking benefit from rcuda Sample scenarios Questions & Answers rcuda Tutorial Middleware /44

144 Outline What is rcuda? Installing and using rcuda rcuda over HPC networks InfiniBand How taking benefit from rcuda Sample scenarios Questions & Answers rcuda Tutorial Middleware /44

145 What is rcuda? CUDA: Node 1 GPU rcuda (remote CUDA): Node 2 Network Node 1 GPU With rcuda Node 2 can use Node 1 GPU!!! rcuda Tutorial Middleware /44

146 Outline What is rcuda? Installing and using rcuda rcuda over HPC networks InfiniBand How taking benefit from rcuda Sample scenarios Questions & Answers rcuda Tutorial Middleware /44

147 Installing and using rcuda Where to obtain rcuda? Software Request Form Package contents. Important folders: doc: rcuda user guide bin: rcuda server daemon lib: rcuda library Installing rcuda Just untar the tarball in both the server and the client(s) node(s) rcuda Tutorial Middleware /44

148 Installing and using rcuda Starting rcuda server: Set env. vars as if you were going to run a CUDA program: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda/lib64 Start rcuda server: cd $HOME/rCUDA/bin./rCUDAd rcuda Tutorial Middleware /44

149 Installing and using rcuda Starting rcuda server: Set env. vars as if you were going to run a CUDA program: Path to CUDA binaries export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda/lib64 Start rcuda server: cd $HOME/rCUDA/bin./rCUDAd rcuda Tutorial Middleware /44

150 Installing and using rcuda Starting rcuda server: Set env. vars as if you were going to run a CUDA program: Path to CUDA libraries export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda/lib64 Start rcuda server: cd $HOME/rCUDA/bin./rCUDAd rcuda Tutorial Middleware /44

151 Installing and using rcuda Starting rcuda server: Set env. vars as if you were going to run a CUDA program: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda/lib64 Start rcuda server: Path to rcuda server cd $HOME/rCUDA/bin./rCUDAd rcuda Tutorial Middleware /44

152 Installing and using rcuda Starting rcuda server: Set env. vars as if you were going to run a CUDA program: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda/lib64 Start rcuda server: cd $HOME/rCUDA/bin./rCUDAd Start rcuda server in background rcuda Tutorial Middleware /44

153 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=<server_name_or_ip_address>:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make EXTRA_NVCCFLAGS=--cudart=shared Run the CUDA program as usual:./devicequery... rcuda Tutorial Middleware /44

154 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=<server_name_or_ip_address>:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make EXTRA_NVCCFLAGS=--cudart=shared Run the CUDA program as usual:./devicequery... Path to CUDA binaries rcuda Tutorial Middleware /44

155 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=<server_name_or_ip_address>:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make EXTRA_NVCCFLAGS=--cudart=shared Run the CUDA program as usual:./devicequery... Path to rcuda library rcuda Tutorial Middleware /44

156 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=<server_name_or_ip_address>:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make EXTRA_NVCCFLAGS=--cudart=shared Run the CUDA program as usual:./devicequery... Number of remote GPUs: 1, 2, 3... rcuda Tutorial Middleware /44

157 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=<server_name_or_ip_address>:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make EXTRA_NVCCFLAGS=--cudart=shared Run the CUDA program as usual:./devicequery... Name/IP of rcuda server rcuda Tutorial Middleware /44

158 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=<server_name_or_ip_address>:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make EXTRA_NVCCFLAGS=--cudart=shared Run the CUDA program as usual:./devicequery... GPU of remote server to use rcuda Tutorial Middleware /44

159 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=<server_name_or_ip_address>:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make EXTRA_NVCCFLAGS=--cudart=shared Run the CUDA program as usual: Very important!!!./devicequery... rcuda Tutorial Middleware /44

160 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=<server_name_or_ip_address>:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make EXTRA_NVCCFLAGS=--cudart=shared Run the CUDA program as usual:./devicequery... rcuda Tutorial Middleware /44

161 Installing and using rcuda Live demonstration: devicequery bandwidthtest rcuda Tutorial Middleware /44

162 Installing and using rcuda Live demonstration: devicequery bandwidthtest Problem: bandwidth with rcuda is too low!! Why? We are using TCP rcuda Tutorial Middleware /44

163 Installing and using rcuda Live demonstration: devicequery bandwidthtest Problem: bandwidth with rcuda is too low!! Why? We are using TCP Solution: HPC networks InfiniBand (IB) rcuda Tutorial Middleware /44

164 Outline What is rcuda? Installing and using rcuda rcuda over HPC networks InfiniBand How taking benefit from rcuda Sample scenarios Questions & Answers rcuda Tutorial Middleware /44

165 rcuda over HPC networks: InfiniBand Starting rcuda server using IB: export RCUDAPROTO=IB cd $HOME/rCUDA/bin./rCUDAd Run CUDA program using rcuda over IB: export RCUDAPROTO=IB cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/bandwidthTest./bandwidthTest rcuda Tutorial Middleware /44

166 rcuda over HPC networks: InfiniBand Starting rcuda server using IB: Tell rcuda we want to use IB export RCUDAPROTO=IB cd $HOME/rCUDA/bin./rCUDAd Run CUDA program using rcuda over IB: Also in the client!! export RCUDAPROTO=IB cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/bandwidthTest./bandwidthTest rcuda Tutorial Middleware /44

167 rcuda over HPC networks: InfiniBand Starting rcuda server using IB: export RCUDAPROTO=IB cd $HOME/rCUDA/bin./rCUDAd Run CUDA program using rcuda over IB: export RCUDAPROTO=IB cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/bandwidthTest./bandwidthTest Live demonstration: bandwidthtest using IB Bandwidth is no more a problem!! rcuda Tutorial Middleware /44

168 Outline What is rcuda? Installing and using rcuda rcuda over HPC networks InfiniBand How taking benefit from rcuda Sample scenarios Questions & Answers rcuda Tutorial Middleware /44

169 How taking benefit from rcuda Sample scenarios: Typical behavior of CUDA applications: moving data to the GPU and performing a lot of computations there to compensate the overhead of having moved the data This benefits rcuda: more computations, less rcuda overhead Scalable applications: more GPUs, less execution time rcuda can use all the GPUs of the cluster, while CUDA only can use the ones directly connected to one node: for some applications, rcuda can get better results than with CUDA rcuda Tutorial Middleware /44

170 How taking benefit from rcuda Three main types of applications: Bandwidth bounded: more transfers, more rcuda overhead Computations bounded: more computations, less rcuda overhead Intermediate rcuda Tutorial Middleware /44

171 LAMMPS Application GPU vs. remote GPU Overhead of remote GPUs? Live demonstration: LAMMPS with CUDA LAMMPS with rcuda rcuda Tutorial Middleware /44

172 LAMMPS Application CPU vs. remote GPU What is better: a local CPU or a remote GPU? Live demonstration: LAMMPS on CPU (without CUDA) rcuda Tutorial Middleware /44

173 LAMMPS Application CPU vs. remote GPU What is better: a local CPU or a remote GPU? Live demonstration: LAMMPS on CPU (without CUDA) LAMMPS on CPU (using all the cores!) rcuda Tutorial Middleware /44

174 LAMMPS Application CPU vs. remote GPU What is better: a local CPU or a remote GPU? Live demonstration: LAMMPS on CPU (without CUDA) LAMMPS on CPU (using all the cores!) What if I am using TCP instead of IB? LAMMPS using rcuda over TCP (1GbE) rcuda Tutorial Middleware /44

175 MAGMA Application GPU vs. remote GPU Overhead of remote GPUs? Live demonstration: MAGMA with CUDA MAGMA with rcuda rcuda Tutorial Middleware /44

176 MAGMA Application CPU vs. remote GPU What is better: a local CPU or a remote GPU? Live demonstration: MAGMA on CPU (without CUDA) rcuda Tutorial Middleware /44

177 MAGMA Application CPU vs. remote GPU What is better: a local CPU or a remote GPU? Live demonstration: MAGMA on CPU (without CUDA) What if I am using TCP instead of IB? MAGMA using rcuda over TCP (1GbE) rcuda Tutorial Middleware /44

178 How taking benefit from rcuda Sample scenarios: Typical behavior of CUDA applications: moving data to the GPU and performing a lot of computations there to compensate the overhead of having moved the data This benefits rcuda: more computations, less rcuda overhead Scalable applications: more GPUs, less execution time rcuda can use all the GPUs of the cluster, while CUDA only can use the ones directly connected to one node: for some applications, rcuda can get better results than with CUDA rcuda Tutorial Middleware /44

179 Multi-GPU scenario CUDA: Multi-GPU App running in Node 1 using its 4 GPUs Node 1 GPU GPU GPU GPU rcuda (remote CUDA): Node 0 Network Node 1 GPU Node 2 GPU Node 3 GPU Node n GPU Multi-GPU running in Node 0 using all GPUs in the cluster rcuda Tutorial Middleware /44

180 Multi-GPU Configuration Configure rcuda for Multi-GPU: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/framework/rCUDAl:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=5 export RCUDA_DEVICE_0=node1:0 export RCUDA_DEVICE_1=node1:1 export RCUDA_DEVICE_2=node2:0 export RCUDA_DEVICE_3=node3:0 export RCUDA_DEVICE_4=node4:0 Check configuration by running devicequery sample rcuda Tutorial Middleware /44

181 Multi-GPU Configuration Configure rcuda for Multi-GPU: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/framework/rCUDAl:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=5 export RCUDA_DEVICE_0=node1:0 export RCUDA_DEVICE_1=node1:1 export RCUDA_DEVICE_2=node2:0 export RCUDA_DEVICE_3=node3:0 export RCUDA_DEVICE_4=node4:0 Number of remote GPUs Check configuration by running devicequery sample rcuda Tutorial Middleware /44

182 Multi-GPU Configuration Configure rcuda for Multi-GPU: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/framework/rCUDAl:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=5 export RCUDA_DEVICE_0=node1:0 export RCUDA_DEVICE_1=node1:1 export RCUDA_DEVICE_2=node2:0 export RCUDA_DEVICE_3=node3:0 export RCUDA_DEVICE_4=node4:0 Location of each GPU Check configuration by running devicequery sample rcuda Tutorial Middleware /44

183 Multi-GPU Configuration Live demonstration: devicequery sample with multiple GPUs LAMMPS multiple remote GPUs MAGMA multiple remote GPUs MonteCarloMultiGPU rcuda Tutorial Middleware /44

184 Outline What is rcuda? Installing and using rcuda rcuda over HPC networks InfiniBand How taking benefit from rcuda Sample scenarios Questions & Answers rcuda Tutorial Middleware /44

185 Get a free copy of rcuda at

186 Hands-on Session (Part II) Carlos Reaño Technical University of Valencia Spain

187 Outline Short intro to CUDA programming Cluster for testing Installing rcuda Running some codes Questions & Answers rcuda Tutorial Middleware /47

188 Outline Short intro to CUDA programming Cluster for testing Installing rcuda Running some codes Questions & Answers rcuda Tutorial Middleware /47

189 Short intro to CUDA programming CUDA programming language = C extended: For running functions in the GPU: called kernels... CUDA API: Functions to copy data from main memory to GPU memory and vice versa... CPU GPU Mem Mem rcuda Tutorial Middleware /47

190 Short intro to CUDA programming CUDA typical code layout: Copy input data from main memory to GPU memory Perform some computation in GPU (launch kernel) Copy output data from GPU memory to main memory CPU GPU Mem Mem rcuda Tutorial Middleware /47

191 Short intro to CUDA programming Sample code: // CUDA Kernel global void mycudakernel(...) { // Perform some computation in the GPU... } int main() { }... // Copy input data to GPU mem cudamemcpy(gpumemptr, memptr, size, cudamemcpyhtod);... // Launch kernel mycudakernel<<<nthreads, nblocks>>>(...);... // Copy output data to main mem cudamemcpy(memptr, gpumemptr, size, cudamemcpydtoh); rcuda Tutorial Middleware /47

192 Outline Short intro to CUDA programming Cluster for testing Installing rcuda Running some codes Questions & Answers rcuda Tutorial Middleware /47

193 Cluster for testing rcu cluster: rcu3 rcu4 rcu5... rcu29 Network (1 GbE) rcu15 GPU GPU GPU rcu16 GPU GPU rcuda Tutorial Middleware /47

194 Cluster for testing rcu cluster: Nodes without GPUs for users (rcuda clients) rcu3 rcu15 GPU rcu4 rcu5... rcu29 Network (1 GbE) rcu16 GPU GPU GPU GPU rcuda Tutorial Middleware /47

195 Cluster for testing rcu cluster: Nodes without GPUs for users (rcuda clients) rcu3 rcu15 GPU rcu4 rcu5... rcu29 Network (1 GbE) rcu16 GPU GPU GPU GPU Nodes with GPUs for rcuda servers rcuda Tutorial Middleware /47

196 Outline Short intro to CUDA programming Cluster for testing Installing rcuda Running some codes Questions & Answers rcuda Tutorial Middleware /47

197 Installing and using rcuda Log into rcu cluster rcuda software package already in $HOME folder Installing rcuda Just untar the tarball in $HOME folder Package contents. Important folders: doc: rcuda user guide bin: rcuda server daemon lib: rcuda library rcuda Tutorial Middleware /47

198 Installing and using rcuda CUDA must be installed in GPU nodes In the nodes running rcuda servers Already installed in our cluster rcuda Tutorial Middleware /47

199 Installing and using rcuda Starting rcuda server: Set env. vars as if you were going to run a CUDA program: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda/lib64 Start rcuda server: cd $HOME/rCUDA/bin./rCUDAd rcuda Tutorial Middleware /47

200 Installing and using rcuda Starting rcuda server: Set env. vars as if you were going to run a CUDA program: Path to CUDA binaries export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda/lib64 Start rcuda server: cd $HOME/rCUDA/bin./rCUDAd rcuda Tutorial Middleware /47

201 Installing and using rcuda Starting rcuda server: Set env. vars as if you were going to run a CUDA program: Path to CUDA libraries export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda/lib64 Start rcuda server: cd $HOME/rCUDA/bin./rCUDAd rcuda Tutorial Middleware /47

202 Installing and using rcuda Starting rcuda server: Set env. vars as if you were going to run a CUDA program: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda/lib64 Start rcuda server: Path to rcuda server cd $HOME/rCUDA/bin./rCUDAd rcuda Tutorial Middleware /47

203 Installing and using rcuda Starting rcuda server: Set env. vars as if you were going to run a CUDA program: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda/lib64 Start rcuda server: cd $HOME/rCUDA/bin./rCUDAd Start rcuda server in background rcuda Tutorial Middleware /47

204 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=rcu16:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make Run the CUDA program as usual:./devicequery... rcuda Tutorial Middleware /47

205 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=rcu16:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make Run the CUDA program as usual:./devicequery... Path to CUDA binaries rcuda Tutorial Middleware /47

206 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=rcu16:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make Run the CUDA program as usual:./devicequery... Path to rcuda library rcuda Tutorial Middleware /47

207 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=rcu16:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make Run the CUDA program as usual:./devicequery... Number of remote GPUs: 1, 2, 3... rcuda Tutorial Middleware /47

208 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=rcu16:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make Run the CUDA program as usual:./devicequery... Name of rcuda server rcuda Tutorial Middleware /47

209 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=rcu16:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make Run the CUDA program as usual:./devicequery... GPU of remote server to use rcuda Tutorial Middleware /47

210 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=rcu16:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make Run the CUDA program as usual:./devicequery... rcuda Tutorial Middleware /47

211 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=<server_name_or_ip_address>:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make Run the CUDA program as usual:./devicequery... rcuda Tutorial Middleware /47

212 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=<server_name_or_ip_address>:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make Run the CUDA program as usual:./devicequery... Error! Why? rcuda Tutorial Middleware /47

213 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=<server_name_or_ip_address>:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/1_Utilities/deviceQuery make EXTRA_NVCCFLAGS=--cudart=shared Run the CUDA program as usual: Very important!!!./devicequery... rcuda Tutorial Middleware /47

214 Installing and using rcuda Running a CUDA program with rcuda: Set env. vars as follows: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/lib:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=1 export RCUDA_DEVICE_0=<server_name_or_ip_address>:0 Compile CUDA program using dynamic libraries: cd $HOME/NVIDIA_CUDA_Samples/6.5/1_Utilities/deviceQuery make EXTRA_NVCCFLAGS=--cudart=shared Run the CUDA program as usual:./devicequery... rcuda Tutorial Middleware /47

215 Outline Short intro to CUDA programming Cluster for testing Installing rcuda Running some codes Questions & Answers rcuda Tutorial Middleware /47

216 devicequery Impact of multiple users sharing the same GPU Measure time of running devicequery sample 10 times when the remote GPU is only used by one user Measure time of running devicequery sample 10 times when multiple users are sharing the same GPU Does execution time increases? With how many concurrent users the increase is more noticeable? rcuda Tutorial Middleware /47

217 devicequery Impact of multiple users sharing the same GPU Measure time of running devicequery sample 10 times when the remote GPU is only used by one user Measure time of running devicequery sample 10 times when multiple users are sharing the same GPU Does execution time increases? With how many concurrent users the increase is more noticeable? devicequery sample: no computations, no transfers rcuda Tutorial Middleware /47

218 bandwidthtest Impact of multiple users sharing the same GPU Measure bandwidth when copying from main memory to remote GPU memory when the remote GPU is only used by one user Measure bandwidth when copying from main memory to remote GPU memory when the remote GPU when multiple users are sharing the same GPU Does bandwidth decreases? With how many concurrent users the decrease is more noticeable? What happens if we increase the size of the transfer? rcuda Tutorial Middleware /47

219 bandwidthtest Impact of multiple users sharing the same GPU Measure bandwidth when copying from main memory to remote GPU memory when the remote GPU is only used by one user Measure bandwidth when copying from main memory to remote GPU memory when the remote GPU when multiple users are sharing the same GPU Does bandwidth decreases? With how many concurrent users the decrease is more noticeable? What happens if we increase the size of the transfer? bandwidthtest sample: no computations, only transfers rcuda Tutorial Middleware /47

220 vectoradd Impact of multiple users sharing the same GPU Measure performance of vector addition when the remote GPU is only used by one user Measure performance of vector addition when multiple users are sharing the same GPU Does performance decreases? With how many concurrent users the decrease is more noticeable? What happens if we increase the size of the vector? rcuda Tutorial Middleware /47

221 vectoradd Impact of multiple users sharing the same GPU Measure performance of vector addition when the remote GPU is only used by one user Measure performance of vector addition when multiple users are sharing the same GPU Does performance decreases? With how many concurrent users the decrease is more noticeable? What happens if we increase the size of the vector? vectoradd sample: computations and transfers rcuda Tutorial Middleware /47

222 matrixmul Impact of multiple users sharing the same GPU Measure performance of matrix multiplication when the remote GPU is only used by one user Measure performance of matrix multiplication when multiple users are sharing the same GPU Does performance decreases? With how many concurrent users the decrease is more noticeable? What happens if we increase the size of the matrix? rcuda Tutorial Middleware /47

223 matrixmul Impact of multiple users sharing the same GPU Measure performance of matrix multiplication when the remote GPU is only used by one user Measure performance of matrix multiplication when multiple users are sharing the same GPU Does performance decreases? With how many concurrent users the decrease is more noticeable? What happens if we increase the size of the matrix? matrixmul sample: computations and transfers rcuda Tutorial Middleware /47

224 matrixmulcublas Impact of multiple users sharing the same GPU Measure performance of matrix multiplication when the remote GPU is only used by one user Measure performance of matrix multiplication when multiple users are sharing the same GPU Does performance decreases? With how many concurrent users the decrease is more noticeable? What happens if we increase the size of the matrix? rcuda Tutorial Middleware /47

225 matrixmulcublas Impact of multiple users sharing the same GPU Measure performance of matrix multiplication when the remote GPU is only used by one user Measure performance of matrix multiplication when multiple users are sharing the same GPU Does performance decreases? With how many concurrent users the decrease is more noticeable? What happens if we increase the size of the matrix? matrixmulcublas sample: computations and transfers rcuda Tutorial Middleware /47

226 Multi-GPU scenario CUDA: Multi-GPU App running in Node 1 using its 4 GPUs Node 1 GPU GPU GPU GPU rcuda (remote CUDA): Node 0 Network Node 1 GPU Node 2 GPU Node 3 GPU Node n GPU Multi-GPU running in Node 0 using all GPUs in the cluster rcuda Tutorial Middleware /47

227 Multi-GPU Configuration Configure rcuda for Multi-GPU: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/framework/rCUDAl:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=5 export RCUDA_DEVICE_0=rcu16:0 export RCUDA_DEVICE_1=rcu16:1 export RCUDA_DEVICE_2=rcu16:2 export RCUDA_DEVICE_3=rcu16:3 export RCUDA_DEVICE_4=rcu15:0 rcuda Tutorial Middleware /47

228 Multi-GPU Configuration Configure rcuda for Multi-GPU: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/framework/rCUDAl:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=5 export RCUDA_DEVICE_0=rcu16:0 export RCUDA_DEVICE_1=rcu16:1 export RCUDA_DEVICE_2=rcu16:2 export RCUDA_DEVICE_3=rcu16:3 export RCUDA_DEVICE_4=rcu15:0 Number of remote GPUs rcuda Tutorial Middleware /47

229 Multi-GPU Configuration Configure rcuda for Multi-GPU: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/framework/rCUDAl:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=5 export RCUDA_DEVICE_0=rcu16:0 export RCUDA_DEVICE_1=rcu16:1 export RCUDA_DEVICE_2=rcu16:2 export RCUDA_DEVICE_3=rcu16:3 export RCUDA_DEVICE_4=rcu15:0 Location of each GPU rcuda Tutorial Middleware /47

230 Multi-GPU Configuration Configure rcuda for Multi-GPU: export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$HOME/rCUDA/framework/rCUDAl:$LD_LIBRARY_PATH export RCUDA_DEVICE_COUNT=5 export RCUDA_DEVICE_0=rcu16:0 export RCUDA_DEVICE_1=rcu16:1 export RCUDA_DEVICE_2=rcu16:2 export RCUDA_DEVICE_3=rcu16:3 export RCUDA_DEVICE_4=rcu15:0 Check configuration by running devicequery sample rcuda Tutorial Middleware /47

231 Outline Short intro to CUDA programming Cluster for testing Installing rcuda Running some codes Questions & Answers rcuda Tutorial Middleware /47

232 Get a free copy of rcuda at

233 Hands-on Session (Part III) Carlos Reaño Technical University of Valencia Spain