high-performance computing

C++ and then run it on an Intel Xeon co- processor. ‘We are not telling customers that they

must move from CUDA to C++ and AMD hardware. We developed this HIP tool to give users the flexibility. You can keep your CUDA source code, you can keep development tools that you are using, your CUDA stack,’ said Baratault. ‘You just “HIPify” your code; convert it from CUDA to C++.’

New tools for open GPU programming HIP is a C++ runtime API and kernel language that allows developers to create portable applications. Te resulting C++ code can be compiled with AMD’s HCC and Nvidia’s NVCC, using the best compilers and tools on the respective hardware. Tis Heterogeneous-Compute Interface for Portability (HIP) gives users more hardware and development-tool options. Additionally, because both CUDA and HIP are C++ languages, porting from CUDA to HIP is much easier than porting from CUDA to OpenCL. AMD reports that the conversion can

convert 100 per cent of the code for a given application automatically. However, Baratault stressed that, for the majority of applications, the HIP tool will convert as much as 95 per cent of an applications code: ‘You will likely have to do a small amount of manual tuning. Tat could be 2-3 hours, up to a couple of weeks – it depends on the code.’ AMD also released new HPC drivers

alongside the new HIP tool. As Baratault explains, this was to alleviate the community’s concerns about AMD’s previous drivers, which are based on consumer GPU drivers rather than being developed specifically for HPC. ‘We have to acknowledge that we were not that good at delivering HPC drivers to the community said Baratault. ‘Our drivers had issues, we fixed them, but they were not really HPC drivers because they were based on our consumer catalyst drivers. We decided to re-write them, being open source and being purely HPC, 64 bit Linux drivers and other HPC specific features.’ Te new AMD tools are not aimed at

increasing performance of applications, although it could be possible to get better price per watt AMD cards in some situations. ‘What we offer is freedom, freedom of choice,’ explained Baratault. ‘Today, you will see more than 300 CUDA-ready applications from ISVs or academics, and thousands and thousands of in-house CUDA codes. Tis is a big asset and we think would send the wrong message if we l

New AMD GPUs further increase memory bandwidth

Based on the third generation AMD Graphics Core Next (GCN) architecture, the AMD FirePro S9300 x2 Server GPU is the world’s first professional GPU accelerator to be equipped with high bandwidth memory (HBM), and the first accelerator compatible with all AMD’s GPUOpen Professional Compute tools and libraries. The GPU delivers up to 13.9 TFLOPS of peak single-precision floating point

competition with 3.5x the memory bandwidth of NVIDIA’s Tesla M40 and 2.1x the memory bandwidth of NVIDIA’s Tesla K80.

performance. The new AMD FirePro S9300 x2 Server HBM allows the AMD FirePro S9300 x2 Server GPU to exceed the

tell users that they should drop CUDA and switch to something different, because CUDA is good, CUDA is very good.’ AMD has already started to engage with the

HPC community to encourage the use of these tools. Te first project involved CGG, a global geophysical services and equipment company, which was using Nvidia GPUs to process and analyse seismic data, geoscience and oil and gas research. Employing AMD’s HPC GPU Computing

soſtware tools available through GPUOpen, and with the help of AMD, CGG converted its



in-house Nvidia CUDA code to OpenCL for seismic data processing running on an AMD FirePro S9150 GPU production cluster. ‘Tey [CGG] can have petabytes or even

zettabytes of raw information that they collect on behalf of national oil companies, then they have to process this raw data to extract something that they can interpret’, said Baratault. ‘Once they have identified a reservoir, then they can find out where to drill – drilling is very expensive, so it is effectively a ‘one shot’ process.’ Baratault explained that CGG was an early

adopter of GPU technology because signal processing algorithms are particularly suited to parallel processing: ‘CGG started back in 2006/7, they were one of the first to jump


Based on third generation AMD Graphics Core Next (GCN) architecture, the AMD FirePro S9300 x2 server GPU delivers up to 13.9 TFLOPS of peak single-precision floating point performance – more than any other GPU accelerator available on the market today for single-precision compute.

on Nvidia CUDA technology. CCG tried different architectures, different products and they decided to port most of their internal codes from pure CPU processing on X86 to GPU using CUDA. Why? Because in 2006/7, CUDA was the only suitable framework that was available.’ In the opinion of Baratault, it was this

monopoly of technology, established by Nvidia, which motivated CGG to investigate the use of other accelerator technologies: ‘Like any other company they would like to have double sourcing for key components and for CGG, GPUs are crucial components.’ By using the HIP tools provided by AMD,

CGG could remove the reliance on Nvidia hardware without tying themselves to AMD. Tis is because the HIP tool ports code into C++ rather than a proprietary format – so CCG could just as easily switch from Nvidia GPUs to Intel coprocessors. ‘Te reason why they went for AMD

hardware, the S9150, is that our boards provide much higher single precision performance, we also have much higher memory bandwidth,’ said Baratault. ‘Te speed of communication between the GPU and its memory is very important for this kind of signal processing algorithm.’ Ultimately, AMD believes that by offering

freedom of choice to the GPU community it can begin to demonstrate that Nvidia is not the only game in town when it comes to GPU application development in HPC. Now, it is up to the HPC community to embrace these tools if they want to support freedom of choice for GPU development. ‘CUDA is great. Nvidia did a great job, but,

if you go with Nvidia you are locked into their solutions,’ concluded Baratault. l

JUNE/JULY 2016 5

Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44