<p>If you want to learn OpenGL X.Y or DirectX A.B then shop for hardware that supports that specification. </p>

<p>If you're using other software (Blender, Maya, 3DSMax, etc) you'll want to make sure it's supported.</p>

<p>If your OS has a history of issues with a particular vendor, adjust accordingly.</p>

<p>Beyond that, it's not going to matter much, especially at the hobbyist level.
Price / performance metrics are still relevant, it's just that the definition of performance is different.</p>

CC BY-SA 3.0
2017-11-14T06:49:34.853Z
What about debugging tools? Do you have any experience with Nsight vs CodeXL? Which has the quickest/easiest edit -> run -> debug cycle?
Ahsan Fayaz
CC BY-SA 3.0
2017-11-14T13:52:27.007Z
Although CodeXL is currently being developed by AMD, you can debug NVidia cards with it as well. I think just OpenCL won't work on Nvidia cards.
I can't say which is better though, and there are more tools (like RenderDoc) out there.
Tare
CC BY-SA 3.0
2017-11-14T14:33:22.750Z
@Tare [OpenCL support is included in the latest NVIDIA GPU drivers](https://developer.nvidia.com/opencl).
Pikalek
CC BY-SA 3.0
2017-11-14T14:47:34.943Z
@Pikalek Okay, but is the debugging of OpenCL automatically supported in CodeXL? I haven't used it for a while, but I always got a warning about that.
Tare
CC BY-SA 3.0
2017-11-14T15:17:25.537Z
@Tare Offhand, I don't know either. My general point is to focus on the big picture, not the small details. To me, casual hobbyist dev means low stakes, casual research.
Pikalek
CC BY-SA 4.0
2019-10-06T11:02:13.143Z
Tried CodeXL on Windows with NVIDIA gpu. Always errors on opencl were displayed. I believe it's only for AMD CPU/GPUs.
KeyC0de
CC BY-SA 3.0
2017-11-13T21:16:13.317Z
2017-11-13T21:16:13.317Z
Pikalek
<p>My current laptop has a fairly old Intel integrated GPU which was good enough for following simple tutorials.</p>

<p>I am now keen on getting to grips with advanced techniques and newer APIs, and so I am looking for a new discrete GPU.</p>

<p>I want to ignore the usual price/performance metric for GPUs, as I assume that's going to be irrelevant for a hobbyist programmer.</p>

<p>Is there a pragmatic reason to prefer AMD over Nvidia or vice versa?</p>

<p>A cursory search shows that some tools are exclusive to one vendor (e.g. Nvidia Nsight), but is one significantly better than the other or are the differences minor?</p>

<p>Will drivers make a difference here also? And finally will I run into a lot of example code specific to one vendor?</p>

<gpu><debugging>
Should I prefer an AMD or Nvidia GPU for studying graphics programming, especially with respect to vendor specific debugging tools and ecosystem?
Ahsan Fayaz
# Should I prefer an AMD or Nvidia GPU for studying graphics programming, especially with respect to vendor specific debugging tools and ecosystem?

(Asked by: username_0 on 2017-11-12)

My current laptop has a fairly old Intel integrated GPU which was good enough for following simple tutorials.

I am now keen on getting to grips with advanced techniques and newer APIs, and so I am looking for a new discrete GPU.

I want to ignore the usual price/performance metric for GPUs, as I assume that's going to be irrelevant for a hobbyist programmer.

Is there a pragmatic reason to prefer AMD over Nvidia or vice versa?

A cursory search shows that some tools are exclusive to one vendor (e.g. Nvidia Nsight), but is one significantly better than the other or are the differences minor?

Will drivers make a difference here also? And finally will I run into a lot of example code specific to one vendor?

**Tags:** gpu, debugging


---

## 1 answers

### Answer by username_1 on 2017-11-13. Score: 3 | Accepted answer

If you want to learn OpenGL X.Y or DirectX A.B then shop for hardware that supports that specification.

If you're using other software (Blender, Maya, 3DSMax, etc) you'll want to make sure it's supported.

If your OS has a history of issues with a particular vendor, adjust accordingly.

Beyond that, it's not going to matter much, especially at the hobbyist level.
Price / performance metrics are still relevant, it's just that the definition of performance is different.

> **Comments:**
> **username_0**: What about debugging tools? Do you have any experience with Nsight vs CodeXL? Which has the quickest/easiest edit -> run -> debug cycle?  
> **username_2**: Although CodeXL is currently being developed by AMD, you can debug NVidia cards with it as well. I think just OpenCL won't work on Nvidia cards. I can't say which is better though, and there are more tools (like RenderDoc) out there.  
> **username_1**: @username_2 [OpenCL support is included in the latest NVIDIA GPU drivers](https://developer.nvidia.com/opencl).  
> **username_2**: @username_1 Okay, but is the debugging of OpenCL automatically supported in CodeXL? I haven't used it for a while, but I always got a warning about that.  
> **username_1**: @username_2 Offhand, I don't know either. My general point is to focus on the big picture, not the small details. To me, casual hobbyist dev means low stakes, casual research.  
> **username_3**: Tried CodeXL on Windows with NVIDIA gpu. Always errors on opencl were displayed. I believe it's only for AMD CPU/GPUs.  

---

