Performance for Game Developers
Game performance work is finding and removing what stops a game hitting its target frame rate. Profilers like the Unity Profiler show CPU, GPU and memory costs. Common fixes include object pooling, batching draw calls, level of detail, culling and avoiding garbage collection spikes.
Stage: Optimisation and Release · Part of the Game Developer roadmap · Last reviewed 19 November 2026
What to learn in Performance
- Identify whether a game is CPU-bound or GPU-bound using a profiler
- Reduce draw calls with batching and atlases
- Implement object pooling for bullets and effects
- Avoid per-frame memory allocations that trigger garbage collection
- Set a frame time budget in milliseconds for each system
Performance interview questions
What is object pooling and why use it?
Pooling creates a set of reusable objects up front and enables or disables them instead of instantiating and destroying them. It avoids allocation costs and garbage collection spikes, which matters for bullets, particles and enemies spawned often.
How do you tell if you are CPU-bound or GPU-bound?
Use a profiler to compare frame time on each side. If lowering resolution improves frame rate, the GPU is the limit; if it does not and scripts or physics dominate, the CPU is the limit. Fix the bottleneck first.
Where Performance fits in the Game Developer roadmap
Performance belongs to the Optimisation and Release stage (intermediate level), which takes about 5 hours. Polish and ship.
Other units in this stage
Back to the full Game Developer roadmap