Performance optimization
Performance work is a measurement discipline, not a bag of tricks. The method is always the
same: profile → find the one bottleneck → fix that → measure again. This skill teaches that
loop and the highest-leverage fixes (pooling, batching, allocation control, asset budgets), and
points you at each engine's profiler. It pairs with physics-tuning for simulation cost.
When to use
- Use when the frame rate is low or uneven, the game stutters/hitches, or it must hit a target
(60 FPS desktop, 30/60 mobile) and currently doesn't.
- Use to decide what to optimize: profile, read the frame budget, and identify whether the CPU
or GPU is the bottleneck before changing any code.
- Use to apply specific fixes: object pooling, draw-call/batch reduction, removing per-frame
allocations and GC spikes, and setting asset budgets.
When not to use: for physics jitter/tunneling/timestep specifically, use physics-tuning.
For the engine's concrete profiler UI and rendering settings, use that
engine skill (godot-export covers some build settings; engine cores cover the rest). This skill
is the cross-engine method and the shared fixes.
The golden rule: measure first, never guess
Most performance "fixes" applied without profiling target the wrong thing and add complexity for
no gain. Do not optimize code you have not measured. Open the profiler, find the single
biggest cost in a representative scene on representative hardware, and fix that. Re-measure to
confirm the fix helped before moving on. Profile a release/optimized build where it matters —
editor and debug builds lie (editor overhead, no compiler optimization).
Core workflow
- Define the target and reproduce. State the goal (e.g. 60 FPS = 16.67 ms/frame) and find a
repeatable worst-case scene. "Sometimes slow" is unfixable; a reproducible spike is fixable.
- Profile before touching code. Run the engine profiler and read the frame: total frame
time, and the split between CPU (game logic, physics, scripts) and GPU (rendering).
- Find the bottleneck — CPU or GPU. If GPU time ≫ CPU, attack draw calls/overdraw/shaders/
resolution. If CPU time dominates, attack scripts/physics/allocations. Fixing the wrong side
does nothing.
- Fix the single biggest cost. Prefer an algorithmic win (do less work, cache, spatial
partition, run less often) over micro-optimizing a hot line. Apply the matching shared fix
(pooling, batching, allocation removal).
- Re-measure on the same scene/hardware. Confirm the number moved. Keep or revert based on
data, not intuition.
- Set budgets so it stays fixed. Per-frame ms budgets per subsystem, plus asset budgets
(texture sizes, triangle counts, draw-call ceilings); add a perf check to verification.
- Report measured numbers. State before/after frame time, the bottleneck found, and the fix
— never "should be faster". If you could only measure in-editor, say so.
Patterns
1. Frame budget math (turn "feels slow" into a number)
target FPS → frame budget: 60 FPS = 16.67 ms | 30 FPS = 33.3 ms | 120 FPS = 8.33 ms
The WHOLE frame (CPU sim + render submit + GPU) must fit the budget; the GPU runs in parallel,
so the slower of CPU-frame and GPU-frame sets your FPS. Allocate sub-budgets, e.g. @60 FPS:
gameplay/scripts ~5 ms · physics ~3 ms · rendering(CPU submit) ~4 ms · UI/other ~2 ms · slack.
If one subsystem blows its slice, that's your target — not whatever you assumed.
2. Measure with the engine profiler (do this before any fix)
Godot 4.7 : Debugger ▸ Profiler (script/physics time) and Monitors tab (FPS, draw calls, memory).
In code: Performance.get_monitor(Performance.TIME_PROCESS) and
Performance.get_monitor(Performance.RENDER_TOTAL_DRAW_CALLS_IN_FRAME).
Unity 6.3 LTS : Profiler window (CPU/GPU/Memory/Rendering modules) + Frame Debugger for draw calls.
In code: a ProfilerRecorder tracking "CPU Main Thread Frame Time" for a HUD/log.
Unreal 5 : `stat unit` (Frame/Game/Draw/GPU ms), `stat fps`, `stat scenerendering` (draw calls);
Unreal Insights for deep traces.
# Read the split: is the Draw/GPU line the biggest, or the Game/CPU line? That decides the fix.
3. Object pooling (stop allocating/freeing in hot loops)
# Bullets, particles, enemies, damage numbers: reuse a fixed set instead of instantiate()/free()
# every frame — that thrashes memory and (in C#) feeds the GC.
var _pool: Array[Node] = []
func acquire() -> Node:
var n: Node = _pool.pop_back() if not _pool.is_empty() else bullet_scene.instantiate()
n.set_process(true); n.visible = true
return n
func release(n: Node) -> void:
n.set_process(false); n.visible = false # disable + hide; DON'T free
_pool.append(n) # back to the pool for reuse
# RIGHT: pre-warm the pool at load; reuse. WRONG: instantiate()/queue_free() per shot.
4. Cut draw calls (the most common GPU-side win)
Each unique material/texture/state change is roughly a draw call; thousands of them stall the GPU.
- Atlas textures and share materials so sprites/meshes batch into one call.
- Identical meshes → GPU instancing (Unity), MultiMesh / MultiMeshInstance (Godot), Instanced
Static Mesh (Unreal).
- Static geometry → static batching / baking; mark non-moving objects static.
- Reduce overdraw: limit large overlapping transparent/particle layers (they re-shade pixels).
- Fewer real-time lights/shadows; bake lighting where it doesn't move.
Measure draw calls before and after — the count should drop, and so should GPU frame time.
5. Kill per-frame allocations (GC spikes = stutter)
// Unity 6.3 LTS (C#). Allocating every frame fills the managed heap; the GC then stalls a frame.
// WRONG (allocates each call): foreach (var e in FindObjectsOfType<Enemy>()) ... // + LINQ, new[]
// RIGHT: cache references once, reuse buffers, avoid LINQ/boxing in Update.
void Update() {
_hits = Physics.RaycastNonAlloc(ray, _hitBuffer); // reuse a preallocated array
for (int i = 0; i < _hits; i++) { /* ... */ } // no per-frame allocation
}
// Godot/GDScript: avoid building new arrays/dictionaries every frame in _process; reuse them.
Pitfalls
- Optimizing without profiling. The intuitive culprit is usually wrong. Measure first, every
time.
- Profiling the editor / a debug build. Editor overhead and unoptimized code mislead. Profile
a release build on target hardware for real numbers.
- Fixing the wrong side. Micro-optimizing CPU code when the GPU is the bottleneck (or vice
versa) changes nothing. Check the CPU-vs-GPU split first.
- Micro-optimizing over algorithm. Shaving a function when an O(n²) loop or a per-frame
full-scene query is the real cost. Reduce the work, don't polish it.
- Instantiate/free in hot loops. Spawning and destroying bullets/particles every frame causes
fragmentation and GC spikes. Pool them.
- Per-frame allocations / LINQ / boxing in
Update (C#) feed the GC → periodic hitches.
Cache and reuse.
- Draw-call explosion from unique materials and unbatched sprites/meshes. Atlas, share
materials, instance, batch.
- Overdraw from stacked transparents/particles/full-screen effects re-shading pixels.
- No budgets. Without per-subsystem ms and asset ceilings, performance silently regresses;
enforce them in your build/CI checks.
- Optimizing too early. Don't contort a prototype for performance before it's fun or measured.
References
- For per-engine profiler walkthroughs, the CPU-vs-GPU triage flowchart, a complete pooling
manager, batching/instancing rules per engine, allocation/GC guidance, LOD/culling, and asset
budgets (texture sizes, triangle counts, audio, mobile thermals), read
references/profiling-and-budgets.md.
Related skills
physics-tuning — simulation cost, fixed-step budget, sleeping bodies, broadphase layers.
godot-export — release/build settings that affect measured performance.
procedural-gen, game-ai — common CPU hotspots (generation, pathfinding) to budget and defer.
roguelike, tower-defense, survival-crafting — entity-heavy genres that need pooling/budgets.
1---2name: game-performance-optimization3description: >4 Find and fix game performance problems methodically — measure with the engine profiler first,5 reason about the frame-time budget, locate the CPU-vs-GPU bottleneck, then apply the right fix:6 object pooling, draw-call batching, fewer allocations/GC spikes, and asset budgets. Engine-7 neutral method that pairs with each engine's profiler. Use when the user mentions performance,8 optimize, low/dropping FPS, frame drops, stutter, lag, profiler, frame budget, draw calls,9 batching, garbage collection/GC spikes, object pooling, or "the game runs slow".10metadata:11 source: https://skillmd.com/skills/junmystery/game-performance-optimization12---1314# Performance optimization1516Performance work is a measurement discipline, not a bag of tricks. The method is always the17same: **profile → find the one bottleneck → fix that → measure again**. This skill teaches that18loop and the highest-leverage fixes (pooling, batching, allocation control, asset budgets), and19points you at each engine's profiler. It pairs with `physics-tuning` for simulation cost.2021## When to use2223- Use when the frame rate is low or uneven, the game stutters/hitches, or it must hit a target24 (60 FPS desktop, 30/60 mobile) and currently doesn't.25- Use to decide *what* to optimize: profile, read the frame budget, and identify whether the CPU26 or GPU is the bottleneck before changing any code.27- Use to apply specific fixes: object pooling, draw-call/batch reduction, removing per-frame28 allocations and GC spikes, and setting asset budgets.2930**When *not* to use:** for physics jitter/tunneling/timestep specifically, use `physics-tuning`.31For the engine's concrete profiler UI and rendering settings, use that32engine skill (`godot-export` covers some build settings; engine cores cover the rest). This skill33is the cross-engine method and the shared fixes.3435## The golden rule: measure first, never guess3637Most performance "fixes" applied without profiling target the wrong thing and add complexity for38no gain. **Do not optimize code you have not measured.** Open the profiler, find the single39biggest cost in a representative scene on representative hardware, and fix that. Re-measure to40confirm the fix helped before moving on. Profile a **release/optimized build** where it matters —41editor and debug builds lie (editor overhead, no compiler optimization).4243## Core workflow44451. **Define the target and reproduce.** State the goal (e.g. 60 FPS = 16.67 ms/frame) and find a46 repeatable worst-case scene. "Sometimes slow" is unfixable; a reproducible spike is fixable.472. **Profile before touching code.** Run the engine profiler and read the frame: total frame48 time, and the split between CPU (game logic, physics, scripts) and GPU (rendering).493. **Find the bottleneck — CPU or GPU.** If GPU time ≫ CPU, attack draw calls/overdraw/shaders/50 resolution. If CPU time dominates, attack scripts/physics/allocations. Fixing the wrong side51 does nothing.524. **Fix the single biggest cost.** Prefer an **algorithmic** win (do less work, cache, spatial53 partition, run less often) over micro-optimizing a hot line. Apply the matching shared fix54 (pooling, batching, allocation removal).555. **Re-measure on the same scene/hardware.** Confirm the number moved. Keep or revert based on56 data, not intuition.576. **Set budgets so it stays fixed.** Per-frame ms budgets per subsystem, plus asset budgets58 (texture sizes, triangle counts, draw-call ceilings); add a perf check to verification.597. **Report measured numbers.** State before/after frame time, the bottleneck found, and the fix60 — never "should be faster". If you could only measure in-editor, say so.6162## Patterns6364### 1. Frame budget math (turn "feels slow" into a number)6566```text67target FPS → frame budget: 60 FPS = 16.67 ms | 30 FPS = 33.3 ms | 120 FPS = 8.33 ms68The WHOLE frame (CPU sim + render submit + GPU) must fit the budget; the GPU runs in parallel,69so the slower of CPU-frame and GPU-frame sets your FPS. Allocate sub-budgets, e.g. @60 FPS:70 gameplay/scripts ~5 ms · physics ~3 ms · rendering(CPU submit) ~4 ms · UI/other ~2 ms · slack.71If one subsystem blows its slice, that's your target — not whatever you assumed.72```7374### 2. Measure with the engine profiler (do this before any fix)7576```text77Godot 4.7 : Debugger ▸ Profiler (script/physics time) and Monitors tab (FPS, draw calls, memory).78 In code: Performance.get_monitor(Performance.TIME_PROCESS) and79 Performance.get_monitor(Performance.RENDER_TOTAL_DRAW_CALLS_IN_FRAME).80Unity 6.3 LTS : Profiler window (CPU/GPU/Memory/Rendering modules) + Frame Debugger for draw calls.81 In code: a ProfilerRecorder tracking "CPU Main Thread Frame Time" for a HUD/log.82Unreal 5 : `stat unit` (Frame/Game/Draw/GPU ms), `stat fps`, `stat scenerendering` (draw calls);83 Unreal Insights for deep traces.84# Read the split: is the Draw/GPU line the biggest, or the Game/CPU line? That decides the fix.85```8687### 3. Object pooling (stop allocating/freeing in hot loops)8889```gdscript90# Bullets, particles, enemies, damage numbers: reuse a fixed set instead of instantiate()/free()91# every frame — that thrashes memory and (in C#) feeds the GC.92var _pool: Array[Node] = []93func acquire() -> Node:94 var n: Node = _pool.pop_back() if not _pool.is_empty() else bullet_scene.instantiate()95 n.set_process(true); n.visible = true96 return n97func release(n: Node) -> void:98 n.set_process(false); n.visible = false # disable + hide; DON'T free99 _pool.append(n) # back to the pool for reuse100# RIGHT: pre-warm the pool at load; reuse. WRONG: instantiate()/queue_free() per shot.101```102103### 4. Cut draw calls (the most common GPU-side win)104105```text106Each unique material/texture/state change is roughly a draw call; thousands of them stall the GPU.107- Atlas textures and share materials so sprites/meshes batch into one call.108- Identical meshes → GPU instancing (Unity), MultiMesh / MultiMeshInstance (Godot), Instanced109 Static Mesh (Unreal).110- Static geometry → static batching / baking; mark non-moving objects static.111- Reduce overdraw: limit large overlapping transparent/particle layers (they re-shade pixels).112- Fewer real-time lights/shadows; bake lighting where it doesn't move.113Measure draw calls before and after — the count should drop, and so should GPU frame time.114```115116### 5. Kill per-frame allocations (GC spikes = stutter)117118```csharp119// Unity 6.3 LTS (C#). Allocating every frame fills the managed heap; the GC then stalls a frame.120// WRONG (allocates each call): foreach (var e in FindObjectsOfType<Enemy>()) ... // + LINQ, new[]121// RIGHT: cache references once, reuse buffers, avoid LINQ/boxing in Update.122void Update() {123 _hits = Physics.RaycastNonAlloc(ray, _hitBuffer); // reuse a preallocated array124 for (int i = 0; i < _hits; i++) { /* ... */ } // no per-frame allocation125}126// Godot/GDScript: avoid building new arrays/dictionaries every frame in _process; reuse them.127```128129## Pitfalls130131- **Optimizing without profiling.** The intuitive culprit is usually wrong. Measure first, every132 time.133- **Profiling the editor / a debug build.** Editor overhead and unoptimized code mislead. Profile134 a release build on target hardware for real numbers.135- **Fixing the wrong side.** Micro-optimizing CPU code when the GPU is the bottleneck (or vice136 versa) changes nothing. Check the CPU-vs-GPU split first.137- **Micro-optimizing over algorithm.** Shaving a function when an O(n²) loop or a per-frame138 full-scene query is the real cost. Reduce the work, don't polish it.139- **Instantiate/free in hot loops.** Spawning and destroying bullets/particles every frame causes140 fragmentation and GC spikes. Pool them.141- **Per-frame allocations / LINQ / boxing in `Update`** (C#) feed the GC → periodic hitches.142 Cache and reuse.143- **Draw-call explosion** from unique materials and unbatched sprites/meshes. Atlas, share144 materials, instance, batch.145- **Overdraw** from stacked transparents/particles/full-screen effects re-shading pixels.146- **No budgets.** Without per-subsystem ms and asset ceilings, performance silently regresses;147 enforce them in your build/CI checks.148- **Optimizing too early.** Don't contort a prototype for performance before it's fun or measured.149150## References151152- For per-engine profiler walkthroughs, the CPU-vs-GPU triage flowchart, a complete pooling153 manager, batching/instancing rules per engine, allocation/GC guidance, LOD/culling, and asset154 budgets (texture sizes, triangle counts, audio, mobile thermals), read155 `references/profiling-and-budgets.md`.156157## Related skills158159- `physics-tuning` — simulation cost, fixed-step budget, sleeping bodies, broadphase layers.160- `godot-export` — release/build settings that affect measured performance.161- `procedural-gen`, `game-ai` — common CPU hotspots (generation, pathfinding) to budget and defer.162- `roguelike`, `tower-defense`, `survival-crafting` — entity-heavy genres that need pooling/budgets.