4 ms·
I'm no graphics programmer. I'm mostly interested in the compute (OpenCL, CUDA) side of things. I don't own an NVidia GPU, so my experience mostly relates to AM
by dragontamer 8y ago
I'm no graphics programmer. I'm mostly interested in the compute (OpenCL, CUDA) side of things. I don't own an NVidia GPU, so my experience mostly relates to AMD.
I'm certainly interested in AMD's Linux "ROCm" push. I really think the programming model there is relatively easy to understand, but there are major flaws in the documentation and implementation.
For example, OpenCL 1.2 on ROCm 2.0 isn't stable enough to run Blender Cycles. Yes, you can render the default cube, but very slowly. On a real scene, Blender Cycles on OpenCL ROCm can take 500+ seconds to compile, and the actual execution seems to hang (infinite loop and/or memory segfault, depending on the scene) on anything close to a typical geometry.
Note that Blender's OpenCL code is explicitly written for AMD's older OpenCL (AMDGPU-Pro OpenCL implementation). Blender has a separate CUDA branch for NVidia cards. So OpenCL ROCm is at very least performance-incompatible with OpenCL AMDGPU-Pro. The Blender OpenCL code probably has to be rewritten to work (ie: not infinite loop), and maybe even become efficient on OpenCL ROCm again.
--------
AMD's hardware is fine (not as power-efficient as NVidia, but performance is fine, in theory). But the drivers / software stack is clearly immature. Even as ROCm has hit a 2.0 release, these sorts of issues still exist.
AMDGPU-PRO with OpenCL1.2 is workable, but feels old and cranky. (OpenCL 1.2 was specified in 2011, and is missing key features. Its atomics model is incompatible with C/C++11, its missing SVM and kernel-side enqueue... etc. etc.)
AMDGPU-PRO OpenCL2.0 is theoretically supported, but is still unstable in my experience. ROCm OpenCL (both 1.2 and 2.0) is still under development, but doesn't seem to be ready for prime-time yet. (At least, with Blender 2.79 or 2.80 Cycles is any indication).
AMD HCC seems usable, but there aren't many programs using it. AMD HIP is an interesting idea but I haven't used it.
I know NVidia has driver issues / software issues. But CUDA Code written 5 years ago will still have similar performance / implementation if run on today's cards, on today's software stack. I'm not sure if the same is true for AMD's OpenCL code (between AMDGPU-PRO OpenCL1.2 and ROCm 1.2).
----------
Long story short: the only mature AMD OpenCL compute platform seems to be OpenCL 1.2 on AMDGPU-PRO. Fortunately, it also seems like AMDGPU-PRO will work for the foreseeable future, but AMD really needs to clarify its platform to attract developers. (Ex: prioritize testing of ROCm OpenCL to ensure performance-compatibility with existing OpenCL 1.2 code written for AMDGPU-PRO)
- shmerl 8y agoIs OpenCL implementation open source in the PRO package?
- dragontamer 8y agoNo. AMDGPU-PRO is closed-source. Which is partially why ROCm exists. Its the OpenSource implementation of AMD's driver stack. AMD seems to have indicated that the Open Source ROCm drivers are the way of the future. Its a sentiment I can certainly get behind (and AMD has even pushed the ROCm driver stack to the Linux Kernel proper). But ROCm isn't ready quite yet. So I think in practice, people will still be relying upon the older AMDGPU-Pro drivers. At least for the next year.
- jacobush 8y agoIt's so interesting that ever since 1998 ATI (AMD) drivers have always been crap and the Nvidia ones good. That's more than 20 years now.
- bryanlarsen 8y agoOn Linux in my experience, Nvidia drivers are crap and have always been crap. AMD have gone from much crappier to almost OK.
- jacobush 8y agoIt's been a while now admittedly for me with Linux, but for me it was like, AMD was always trying to halfheartedly support open source, their proprietary drivers fast but buggy and hard to install. The open source driver slow and stable. Nvidia made no pretense, you downloaded a thin open source shim, typed "make" and then it worked and was fast. And 99.9% proprietary blob.
- bryanlarsen 8y ago"and then it worked" not my experience