3 ms·

> It seems to be very specifically about compute, which is not what most people buy their GPUs for. Interestingly, your former "does not work" comment didn't ev

> It seems to be very specifically about compute, which is not what most people buy their GPUs for. Interestingly, your former "does not work" comment didn't even mention that. It's an anecdote. There are many more like it. However, compute is increasingly common, and I suspect we're hitting a critical point with tools like Stable Diffusion. > No timeline (is this 2016? 2018? 2020? 2021?). Particularly, ROCm today has nothing to do with ROCm two years ago. "Great GPU shortage" places it a bit after COVID hit. > We know nothing about your application (what are you even trying to do?) NLP, if you care, but that's true across most compute applications. > GPU model and Vendor are omitted, so we cannot verify your story about support removal It's a conversation, not a jury trial. RX570, if you care. > Libraries "you want to use" are omitted, so we cannot check today's status of ROCm support. If it please the court, the most popular NLP library for the type of work I do is: https://spacy.io/usage https://spacy.io/usage If it please the court, I was also using Cupy extensively, which has experimental ROCm support, which completely didn't work. It isn't officially supported either: https://docs.cupy.dev/en/stable/install.html https://docs.cupy.dev/en/stable/install.html If it please the court, I just made my own library which is tied to CUDA as well, not for lack of trying to make it work with ROCm. AMD will have a bit more of a hole to dig out of if it ever tries to be competitive.

snvzz 4y ago
>"Great GPU shortage" places it a bit after COVID hit. >RX570 My condolences. I was lucky enough to get a Vega 64 (Sapphire's) on launch. I'm still using it today. RDNA3, together with new electricity prices, might finally get me to upgrade. >If it please the court, I just made my own library which is tied to CUDA as well, HIP is meant to solve that problem. Your library might be auto-convertable. It's pretty much CUDA with everything renamed to HIP. It can then run on both CUDA and ROCm.
- frognumber 4y ago
  Here's my basic problem. Neither I, nor anyone I work with, want to understand what "Vega 64 (Sapphire)" or any other of this stuff is. I'd just like things to work. I bought a card advertised to work with ROCm, and got 9 months of use from it, which was just about enough to set up a development environment, since most of the real work is in data engineering, dashboarding, etc. I did take the time to understand this when things broke, but that's not really a reasonable expectation. My recollection of this will be: "AMD market tools at the stability and maturity of early prototypes as production-grade code" and "AMD GPUs might stop working in a few months if AMD gets bored." Experiences like this DO burn customers. If AMD had advertised this as being not-quite-ready for prime-time, I would not have felt bad. The gap between advertising, fine-print, and reality was astronomical. You could point me to github issues and say all this was public, but that's not reasonable to expect of someone buying a GPU. If I walk into a store, and walk out with a card labeled for ROCm, then ROCm should work. One of my colleagues bought an ancient NVidia card, during the same shortage. It just works.

snvzz 4y ago

>"Great GPU shortage" places it a bit after COVID hit. >RX570 My condolences. I was lucky enough to get a Vega 64 (Sapphire's) on launch. I'm still using it today. RDNA3, together with new electricity prices, might finally get me to upgrade. >If it please the court, I just made my own library which is tied to CUDA as well, HIP is meant to solve that problem. Your library might be auto-convertable. It's pretty much CUDA with everything renamed to HIP. It can then run on both CUDA and ROCm.

frognumber 4y ago
Here's my basic problem. Neither I, nor anyone I work with, want to understand what "Vega 64 (Sapphire)" or any other of this stuff is. I'd just like things to work. I bought a card advertised to work with ROCm, and got 9 months of use from it, which was just about enough to set up a development environment, since most of the real work is in data engineering, dashboarding, etc. I did take the time to understand this when things broke, but that's not really a reasonable expectation. My recollection of this will be: "AMD market tools at the stability and maturity of early prototypes as production-grade code" and "AMD GPUs might stop working in a few months if AMD gets bored." Experiences like this DO burn customers. If AMD had advertised this as being not-quite-ready for prime-time, I would not have felt bad. The gap between advertising, fine-print, and reality was astronomical. You could point me to github issues and say all this was public, but that's not reasonable to expect of someone buying a GPU. If I walk into a store, and walk out with a card labeled for ROCm, then ROCm should work. One of my colleagues bought an ancient NVidia card, during the same shortage. It just works.