What causes an unknown performance bottleneck?

Frame rate is limited by whichever of CPU or GPU finishes last each frame, and optimizing the one that is not the bottleneck changes nothing — so you must measure which it is first.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Find Whether Your Game Is CPU- or GPU-Bound

Quick answer: Use a profiler to compare CPU frame time against GPU frame time; the larger one is your bottleneck. Then apply CPU fixes (draw calls, logic, GC) or GPU fixes (overdraw, shaders, resolution) accordingly.

The most common optimization mistake is improving the part that was never the limit. Measuring whether you are CPU- or GPU-bound tells you where every minute of effort should go. Here is how.

How to fix it

1. Measure CPU and GPU frame time

A profiler shows main-thread (CPU) time and GPU time per frame. Whichever is larger is the bottleneck. If lowering resolution raises frame rate, you are GPU-bound; if it does nothing, you are CPU-bound.

2. Fix the CPU side

If CPU-bound, target draw calls, gameplay and physics logic, and garbage collection. The GPU is idle waiting; making shaders cheaper will not help until the CPU keeps up.

3. Fix the GPU side

If GPU-bound, target overdraw, shader complexity, resolution, and post-processing. Reducing object logic will not help until the GPU stops being the long pole.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every your game error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

The errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.