game-perf

Reduce garbage collection pauses by applying allocation-free patterns to your game loop. This skill enforces in-place updates, object pooling, and reusable scratch buffers to minimize per-frame allocations and stabilize frame times.

Using map, filter, or spread operators causes frame drops because they generate temporary objects inside the update loop. These per-frame allocations increase GC pressure, which leads to latency spikes and uneven frame pacing during gameplay.

The best way to handle per-frame allocations for particle systems and collision detection is implementing object pooling and context objects. Reusing objects instead of allocating new ones prevents garbage collection pauses in tight physics and render paths.

Yes, you can apply zero-allocation patterns to AI update code, render paths, and physics loops. The skill targets all per-frame code, enforcing allocation-free techniques like reusable buffers to ensure smoother frames and lower latency.

You should not use object pooling for objects that are rarely instantiated or destroyed, as the pool memory overhead outweighs the benefits. Pooling is specifically for frequent, per-frame allocations in hot-path game code like entity updates.