unity-profiling
Installation
SKILL.md
unity-profiling — measure the work, then compare the table
"It feels smoother now" survives exactly until someone else plays it. A frame time on its own is barely better: one number, from one moment, on one machine, with nothing to hold it against.
Load what the situation needs
| The situation | Read |
|---|---|
| Starting from nothing; "how many draw calls is this"; "which counters exist on my version"; a counter reads zero | reference/counters.md |
| "The frame rate drops when…" — taking the measurement: warm-up, window size, run modes, the log line and the JSONL schema | reference/frame-windows.md |
| "It hitches when the third pickup spawns" — hitches around spawning, streaming or pooling; a system that builds the same thing twice | reference/work-counters.md |
| "did my change actually help"; building the before/after table; a comparison that refuses | reference/compare.md |
| A window in hand and no cause yet: first-appearance hitch, GC, synchronous loads, distant geometry | reference/where-the-time-goes.md |
| No counter names the cost and you need the marker inside the frame | reference/raw-capture.md |
| A frame-time budget that a test fails on, every run, against this machine's recorded baseline | reference/perf-tests.md · templates/PerfRegressionTest.cs |
"is it the GC" and whose: allocation calls per Update and LateUpdate phase; GetAllocatedBytesForCurrentThread reads 0 |
reference/gc-per-phase.md · resources/GcAllocProbe.cs |
| Memory grows by a step each time a screen or match is rebuilt; runtime materials and meshes | reference/runtime-asset-leaks.md · resources/OwnedAssets.cs · templates/AssetLeakSoakTest.cs |
| A frame time read on a shared machine; post-processing cost; CPU or GPU in the Editor | reference/frame-hygiene.md |