Skip to content
The Technical ArtistArt. Code. Pipelines. Games.
section 05-b
performance
7 guides + tool

Frames Are A Budget. Spend Them Well

Start a performance investigation by finding the bottleneck, then measure the effect of one change. At 60fps the frame budget is about 16.6ms. These guides explain how to inspect that time and use asset checks to find work worth investigating.

Three conceptual frame-time bars become shorter across successive optimisation passes.
performance - frame times, descending
The golden rule

Don't Optimise Blind

Never change code, settings, or content before confirming which thread and system is the actual bottleneck. Fixing the wrong subsystem wastes time and can make the real problem worse. Measure, change one thing, measure again.

Illustrative rendering work blocks within a 16.67 ms target at 60 fps, with a reminder that CPU and GPU stages can overlap.
fig 07 - an illustrative 16.67 ms frame budget at 60 fps
MAP

The Guides

16.6ms @ 60fps
33.3ms @ 30fps
3threads to check
1bottleneck at a time
"The frame doesn't care how beautiful the asset is. It cares how many milliseconds it costs."
Every optimisation conversation starts with the same question: which thread?