Unity devs: stop starving your frame rate

Unity developers still see GC pauses of 5–10 ms per frame, enough to drop a 60 FPS game into a noticeable stutter [Unity Blog]. The problem is unmanaged allocations in hot code paths – string concatenations, List<T> resizes, and LINQ queries that allocate enumerators on every frame. Unity 2025.2 added full support for .NET 8, bringing Span<T> and Memory<T> into the runtime without extra packages [Unity Blog].

The dev.to guide shows how to combine these tools with allocation-free patterns, demonstrating three concrete replacements: StringBuilder for immutable string construction, ArrayPool<T> for temporary buffers, and manual loops instead of LINQ for collection filtering [DevTo]. Each pattern eliminates at least one heap allocation per call. Reducing allocations by 80 % shrinks pause time to under 2 ms, keeping the frame budget intact.

A first-person shooter that previously capped at 120 concurrent players due to per-frame allocations can sustain 200 players after swapping List<T> for ArrayPool<T> and Span<T> buffers, according to a Unity performance case study [DevTo]. Teams that adopt these APIs report a 30 % reduction in total allocation count across typical gameplay loops, as measured by Unity’s Profiler [Unity Blog].

Adopting these patterns does not require a rewrite of the entire codebase. Start by replacing string concatenations with a static StringBuilder, rent temporary arrays from ArrayPool<T>, and rewrite LINQ-heavy sections as manual loops. The result is a smoother frame rate, lower CPU usage, and a more polished player experience.