DLPrimitives Blog :: Internals http://blog.dlprimitives.org/ Development Blog Hello Pytorch OpenCL http://blog.dlprimitives.org/post/5 http://blog.dlprimitives.org/post/5 <div style="direction:ltr"> <p>TL;DR: I managed to run an inference of alexnet using OpenCL/DLPrimitives based pytorch backend!</p> <h2>Details</h2> <p>I started from this <a href="https://pytorch.org/tutorials/advanced/extend_dispatcher.html">tutorial</a> to implement out of source backend for pytorch. It wasn't that simple and I had to do <a href="https://github.com/artyom-beilis/pytorch/commit/eb74af18af6e90ae47f24997af8468bf7b9deb72">small changes</a> in original pytorch source code but finally something is working:</p> <p>Now I implemented only handful of ops and mostly for forward computations: <a href="https://github.com/artyom-beilis/pytorch_dlprim">github backend code</a>. However, I managed to do forward computations and get correct result on pretrained alexnet.</p> <pre><code>$ python validate_network.py --model alexnet --device cuda *.ppm cat.ppm,281,tabby dog.ppm,207,golden retriever parrot.ppm,87,African grey $ python validate_network.py --model alexnet --device opencl:1 *.ppm Accessing device #1:GeForce GTX 960 on NVIDIA CUDA cat.ppm,281,tabby dog.ppm,207,golden retriever parrot.ppm,87,African grey </code></pre> <p>Performance for this tiny task isn't not brilliant, but not horrible either, GTX 960, alexnet batch size of 16 images 224x224:</p> <ul> <li>Pytorch Cuda/CUDNN: 15.317 ms - updated 2021-10-10</li> <li>Pytorch OpenCL/DLPrimitives: 22.932 ms - updated 2021-10-10</li> <li>DLPrim - microframework: 22.401 ms</li> <li>Caffe/CuDNN: 16.1812 ms</li> <li>Caffe/OpenCL: 41.072 ms</li> <li>Caffe/OpenCL+DLPrimitives: 28.618 ms</li> <li>Keras/CuDNN: 23.341 ms</li> <li>Keras/PlaidML: 44.041 ms</li> </ul> <p>Now, one of the issues that I currently have is synchronous execution that gives significant penalty for every operation. I need to understand an asynchronous execution and memory management stuff before I continue. The penalty for NVidia OpenCL backend isn't horrible but it is devastating for AMD OpenCL driver. Need to dive in.</p> <p>Keep updated.</p> <h2>Edit, Oct 10, 2021</h2> <p>I found the way to implement asynchronous execution + initial GPU memory caching. That allowed to be bring the performance of pytorch OpenCL to same level as vanilla dlprimitives. This also solved the performance issues I had with AMD GPU.</p> <p>Additionally I found that I didn't take in an account host-to-device transfer in pytorch benchmarks - so original CUDA run time for pytorch increased.</p> </div> Why do we need OpenCL based deep learning? http://blog.dlprimitives.org/post/2 http://blog.dlprimitives.org/post/2 <div style="direction:ltr"> <p>Why do we need OpenCL based solution for deep learning?</p> <p>NVidia provides high performance tools like cuDNN and TensorRT that power AI industry running CUDA API. AMD does the same for their compute cards with ROCm/MIOpen using their own CUDA clone called "hip".</p> <p>Why should we care? We have a working solution why do we need to reimplement something that already exists with something that likely going to have lower performance?</p> <p>The problem is somewhat deeper than that. I'll talk about 3 points.</p> <ol> <li>We need open source high performance low level algorithms especially for research purposes.</li> <li>We need to use unified GPU API that is standard, open and vendor independent.</li> <li>We need a worthy competition that would lead to better and more affordable products.</li> </ol> <h2>Open source algorithms are mandatory</h2> <p>A good example is a convolution algorithm. In the beginning of DL boom the most common approach was to run <a href="https://petewarden.com/2015/04/20/why-gemm-is-at-the-heart-of-deep-learning/">im2col with GEMM</a> combination that gave decent performance thanks to very efficient cublas library.</p> <p>However it was found that it is much better to merge two GPU kernels - one that converts image to a matrix and another that computes matrix multiplication to a single kernel. However, if you want to implement this technique and check its efficiency you need to have an efficient implementation of core matrix multiplication algorithm in first place. Also matrix multiplication seems like a simple task, in fact it is one of the <a href="https://cnugteren.github.io/tutorial/pages/page1.html">most complicated alorithms to implement in GPU</a></p> <p>If a researcher wants to add a new method of convolution, lets say dilation with variable steps or any other kind of modification it wouldn't be possible to do this efficiently without easily available source code. On the other hand if a researcher wants to improve some performance aspects of the Conv+GEMM algorithm he need to implement what nVidia engineers did in assembly to be able to compare his new implementation to what is done in cuDNN.</p> <p>I would say a good example of such a case would be Winograd Convolution. There is <a href="https://arxiv.org/pdf/1509.09308.pdf">a widely cited paper</a> that describes the algorithm. In reality, there are virtually 0 details about specific implementation. How do you load/store data to shared memory without bank conflicts? how do you perform computations? How do you store and convert results between shared memory to main one? And so on. I personally attempted to implement it several times and couldn't even reach a GEMM based convolution performance.</p> <p>Only <a href="https://www.cse.ust.hk/~weiwa/papers/yan-ppopp20.pdf">this paper from 2020</a> had cleared many low level details an allowed me writing a relatively efficient kernel. It still does not reach the performance of cuDNN implementation but it is way better than GEMM based convolution.</p> <p>Unfortunately, this is a typical case, if tomorrow somebody wants to implement an additional variant of convolution or any other algorithm and prove its efficiency, it is first needed to overcome the performance of unknown highly optimised code to prove that you did something efficient.</p> <p>Thus having open source low level algorithms is very critical for research and the field itself. It is very clear to me why NVidia do not want to release the source code - it contradicts their interest as a monopoly in the field.</p> <p>However the community that works in the field is hurt by this policy. We need faster and more efficient software to solve real world problems, without having the source code of core components the progress in the field may be much slower.</p> <h2>Open and Standardised API</h2> <p>I recently discovered that I can't run a code that was compiled with cuda10 and cudnn7 on RTX 30 series of GPU. I didn't want any of the new GPU features - just wanted to run the program. I couldn't. I need to rebuild the software from the scratch with a new API.</p> <p>What do you think would happen in the gaming industry if NVidia would told the game developers who released their games a year ago to rebuild them from the scratch to be able to run on RTX 3060?</p> <p>It isn't only user unfriendly, it is also sometimes impossible because the team isn't actively developing a product any more and moved to a new one.</p> <p>Of course this does not happen in the gaming world, there are standard open or proprietary APIs: OpenGL, Vulkan and Direct3D. To get a new card you need to install a driver. The rest is the same. You can run today a classic old game like <a href="https://en.wikipedia.org/wiki/Jane%27s_IAF:_Israeli_Air_Force">Jane's IAF: Israeli Air Force</a> on Windows 10 on modern hardware.</p> <p>There is a standard GPU compute API: <a href="https://en.wikipedia.org/wiki/OpenCL">OpenCL</a>. It works very well, it works on virtually every modern GPU from 1st release date: NVidia, AMD, Intel. It even runs on your Android phone's GPU.</p> <p>Kernels that are written for OpenCL or CUDA can be mechanically converted between the platforms as is. Virtually all concepts of OpenCL and CUDA are identical, code is similar.</p> <p>This is highly critical for software maintainability and long-term support.</p> <p>Of course, there are many cases you can't have same kernel running equally efficient on AMD, NVidia, Intel and Mali GPUs. It is true for GEMM and Convolution kernels, but it true to much lesser degree for vast majority of other kernels that do basic but important stuff. Kernels for activation, normalization, element-wise operators and many many others can run same code on different platforms with only minute tweaks.</p> <p>So as long as you have optimised kernels for critical parts, rest can be shared across platforms. It can be compared to writing a code in C or C++ for all platforms like Intel, ARM and MIPS and only small computationally intensive parts are implemented using platform specific assembly on intrinsic code.</p> <p>Finally, if you look into gaming industry dealing with GPUs on daily basis you would clearly understand how the requirement of rebuilding your entire code base upon arrival of new GPU generation is ridiculous. But today it is the sad reality.</p> <p>Open standards are always better than best proprietary ones. Even if you loose something now you are winning in long-term run.</p> <h2>Monopoly Issue</h2> <p>It isn't a secret that NVidia controls virtually all deep-learning and GPU-compute market. It goes to that level that AMD creates "hip" - virtually implemented cuda API with fast replacement of <code>s/cuda/hip/</code> just to be able to run NVidia's code. As long as vendor specific API is used, you will remain under the control of this vendor.</p> <p>It isn't the case in Gaming. AMD, Intel and NVidia always try to challenge each other to this degree or other while we as customers enjoy better and more affordable products, enjoy new features like Ray Tracing etc.</p> <p>It isn't the case for deep-learning. NVidia can charge premium for their "professional" grade devices that provide virtually same silicone. Why? Because they really can. If I was NVidia's CEO I would do the same.</p> <p>Just to make it clear, currently NVidia is superior DL platform over AMD and Intel, mostly due to absolute ignorance of software by AMD and lack of any kind of powerful GPUs from Intel.</p> <p>But even if you rightfully use NVidia, relying on open API and open source libraries will allow you to both challenge NVidia that does not take competition seriously and have much lesser headache when NVidia releases a new GPU.</p> <p>And what is more important you are empowered to choose whatever product you or your customer want or has and not be limited to a single vendor.</p> <h2>Additional Points</h2> <h3>Why not <a href="https://en.wikipedia.org/wiki/SYCL">SYCL</a>?</h3> <p>The answer is actually very simple. There are several points that make OpenCL superior:</p> <ol> <li>The fact that the kernel source code is separate from C++ code actually makes it much more portable. Mixing <code>C++</code> and GPU code the way it is done in CUDA it is nice to start with but brings lots of <a href="https://dev-discuss.pytorch.org/t/cuda-loops-case-study-code-generation-vs-templates/302">issues in long term</a> where you need to compile for numerous platforms and combinations.</li> <li>Many <a href="https://en.wikipedia.org/wiki/SYCL#Implementations">SYCL Implementation</a> target one platform only instead of being cross platform.</li> <li>There are still no serious working open source SYCL implementation, while OpenCL is working today on virtually every device</li> </ol> <h3>Why wouldn't AMD or Intel create an alternative?</h3> <p>Good question. And this is should be addressed to them.</p> <p>AMD created hip and MiOpen that aren't even compatible with their own RDNA hardware, started dropping support of older GCN (like rx580) and limited to Linux only. Their investment into deep learning is minimalist to none.</p> <p>Intel played along and actually created OpenCL implementations. However their product oneDNN is optimised for Intel and wrapped cuDNN for NVidia.</p> <p>Bottom line, each vendor cares about his own interests, probably they decided that this is a lost battle.</p> <p>However the good thing that both AMD and Intel published <a href="https://github.com/ROCmSoftwarePlatform/MIOpen/issues/480">almost</a> everything as open source so it makes easier in future to use their work in critical training paths.</p> </div>