unity-performance

To find Unity performance bottlenecks, analyze script patterns and profiler data to identify hot paths like Update-heavy loops and expensive API lookups. This focused review surfaces top culprits causing frame time spikes without speculative micro-optimizations.

High GC pressure in Unity games is caused by per-frame allocations and mismanaged object lifecycles. Analyzing code for hot paths and applying object pooling reduces these allocations, directly mitigating garbage collection spikes and frame drops.

Optimize Unity Update loops by detecting hot path patterns in Update, FixedUpdate, and LateUpdate. Replacing expensive lookups like GetComponent and Camera.main with cached references reduces frame time spikes and improves runtime performance.

Use object pooling in Unity to manage object lifecycles and eliminate per-frame allocations. Applying pooling within hot paths reduces GC pressure and stabilizes frame time during gameplay by reusing instances instead of instantiating new ones.

Camera.main causes performance issues in Unity because it performs an expensive internal lookup every call. Detecting this misuse within hot paths allows you to cache the reference, eliminating repeated expensive searches and reducing frame time.

Yes, this skill can analyze physics updates for frame time spikes by detecting mis-timed updates within FixedUpdate loops. It identifies these hot paths and advises on optimizing physics interactions to stabilize overall gameplay framerate.