Skip to main content

Performance for Unitys

Unity performance work is the process of measuring and reducing the time and memory a game uses. The Profiler records CPU, rendering and memory usage per frame, and the Frame Debugger shows draw calls. Common fixes include batching, pooling, reducing garbage allocation, and lowering overdraw and texture memory.

Stage: Optimise and Release · Part of the Unity roadmap · Last reviewed 19 November 2026

What to learn in Performance

Performance interview questions

What causes garbage collection spikes in Unity and how do you avoid them?

Frequent heap allocations such as creating new objects, string concatenation, LINQ and boxing in Update leave garbage that the collector must clear, causing hitches. Cache references, reuse collections, use pooling and avoid per-frame allocations. The Profiler shows allocation per frame.

How do you decide whether a game is CPU-bound or GPU-bound?

Use the Profiler to compare frame time on the main thread and render thread, and check GPU timings where available. If scripts and physics dominate, it is CPU-bound. If rendering time is high while CPU waits, it is GPU-bound. Test by lowering resolution to see the change.

Where Performance fits in the Unity roadmap

Performance belongs to the Optimise and Release stage (intermediate level). Ship the game.

Back to the full Unity roadmap