How do I find which GPUs my game runs slow on?

Capture performance data segmented by GPU vendor and model, then look for where the slowness concentrates: one vendor, one architecture, integrated GPUs, or certain drivers. Performance monitoring with device context lets you see the game is fine on most GPUs but poor on specific ones, even hardware you don't own, turning 'slow for some players' into a targetable diagnosis.

How do I fix a rendering path that's slow on one GPU?

Once you've identified the affected GPU and the expensive rendering, optimize the path to be cheaper everywhere if possible, or provide an alternate, cheaper rendering approach for the affected GPUs (detecting them and using the proper path elsewhere). For an unsupported-feature emulation fallback, avoid relying on that feature on GPUs lacking it. Test the fix on the affected hardware or via field data.

Why Does My Game Run Slow Only on Certain GPUs?

Q: Why does my game run slow only on certain GPUs?

Because GPUs from different vendors and architectures handle rendering differently, so a path that's cheap on most can be expensive on a specific one: an expensive shader/rendering path on that architecture, an unsupported feature falling back to slow emulation, a driver quirk, or integrated-GPU weakness on memory-heavy rendering. The slowness concentrates on particular GPUs because of how they handle a specific part of your rendering.

Quick answer: Your game runs slow only on certain GPUs because something in your rendering is expensive specifically on that hardware: a shader or rendering path that's cheap on most GPUs but costly on that vendor/architecture, a feature that's unsupported and falling back to slow emulation, a driver quirk, or integrated-GPU weakness on memory-heavy rendering. Different GPUs handle rendering differently, so a cheap path on one can be expensive on another.

Performance that's good on most GPUs but poor on certain ones is a targeted problem, the game runs well for most players but badly for those on particular graphics hardware. GPUs from different vendors and architectures handle rendering differently, so identifying the GPU-specific cause is the key to fixing it without hurting performance elsewhere.

Why Performance Varies by GPU

Different GPUs have different performance characteristics, so the same rendering work can cost very differently across them. Causes of GPU-specific slowness: an expensive shader or rendering path on a particular architecture (cheap on most GPUs but hitting a slow path on that one), an unsupported feature falling back to slow emulation on that GPU (it 'works' but slowly), driver quirks handling something inefficiently, and integrated-vs-discrete differences (integrated GPUs are weaker and share memory, so memory/bandwidth-heavy rendering is disproportionately slow).

The pattern, fine on most GPUs, slow on specific ones, points at how those GPUs handle a particular part of your rendering, which differs from the GPUs that run it well.

How to Diagnose and Fix It

Segment performance by GPU, you need to know which GPUs are slow. Capture performance data tagged with GPU vendor and model and look for where the slowness concentrates (one vendor, architecture, integrated GPUs, certain drivers). Bugnet's performance monitoring captures performance across real hardware with device context, so you can see the game is fine on most GPUs but poor on specific ones, even hardware you don't own.

Then, ideally profile on that GPU to find the expensive rendering, and either optimize it to be cheaper everywhere or provide an alternate, cheaper path for the affected GPUs. See our guide on fixing slow performance only on certain GPUs for the details. The GPU-level segmentation makes 'slow for some players' into a targetable 'slow on these specific GPUs.'

Slow on certain GPUs means a rendering path that's cheap elsewhere is expensive on that hardware. Segment performance by GPU to find it, then optimize or provide an alternate path.