How do I reduce stutter in my game?

Cut per-frame allocations (for GC stutter, the leading cause), spread occasional heavy work across frames, and move blocking operations off the main thread, so frame times become consistent. Stutter is intermittent frame time spikes amid smooth play, usually from periodic heavy work. The dominant cause in managed-memory engines is garbage collection: per-frame allocations build up garbage that triggers periodic GC pauses that hitch the frame, so cut per-frame allocations (pool objects, avoid allocating in hot paths, reuse buffers) to reduce GC stutter. Also spread occasional heavy operations across frames (so they do not spike one frame), and move blocking work (loading, I/O) off the main thread (so it does not hitch frames). Bugnet captures performance data including frame time consistency, so you can confirm your game has stutter (periodic frame time spikes) and its pattern (periodic suggests GC), address the cause, and verify per version that frame times became consistent on real devices, smoothing the stutter at its source.

How do I reduce garbage collection stutter?

Reduce per-frame memory allocations, pool reusable objects, avoid creating garbage in hot paths, and minimize temporary allocations, so garbage collection runs less frequently and lighter. GC stutter comes from your game allocating memory frequently (creating garbage), which builds up and triggers periodic GC pauses that hitch the frame. So reduce the garbage, especially per-frame: avoid allocating new objects, arrays, strings, or temporary data every frame in hot paths (the main garbage source), pool reusable objects (reuse rather than create-and-destroy), avoid hidden allocations (some operations allocate behind the scenes), and reuse buffers and collections. With little per-frame garbage, GC runs rarely and lighter, eliminating the periodic pauses. Bugnet captures frame time data, so you can confirm GC stutter (periodic frame time spikes) and, after reducing allocations, verify per version that the stutter smoothed on real devices, confirming your allocation reductions eliminated the GC hitches players experienced.

What's the difference between stutter and a low frame rate?

A low frame rate is consistently slow (every frame takes too long), while stutter is inconsistent (mostly smooth with periodic hitches), with different causes and fixes. A low frame rate is a consistent problem: the game runs below target steadily, every frame too long, usually from doing too much work overall for the hardware, fixed by reducing the per-frame load. Stutter is an inconsistency problem: the frame rate is mostly fine but periodically a frame takes much longer (a hitch), usually from periodic spikes like garbage collection pauses, occasional heavy operations, or main-thread hitches, fixed by eliminating those spikes (reducing allocations for GC, spreading work, moving blocking work off the main thread). The diagnostic difference: low frame rate shows consistently high frame times, stutter shows mostly-good frame times with periodic spikes. Bugnet captures frame time consistency (not just average), so you can distinguish a low frame rate from stutter on real devices, diagnosing which you have and verifying the appropriate fix per version, since treating one like the other would target the wrong cause.

Ways to Reduce Stutter

Quick answer: Cut per-frame memory allocations (the leading cause of GC stutter), spread occasional heavy work across frames, and move blocking operations off the main thread, stutter is intermittent frame time spikes, often GC-driven.

Stutter, periodic hitches amid smooth play, makes a game feel rough even at a good average frame rate. Here are the best ways to reduce stutter.

Cut Per-Frame Memory Allocations

Reduce stutter by cutting per-frame memory allocations, the leading cause of garbage collection stutter, pool reusable objects, avoid allocating in hot paths, and reuse buffers, so garbage collection runs less and lighter. Less garbage means fewer GC hitches.

Bugnet captures performance data including frame time consistency, so you can confirm GC stutter (periodic frame time spikes) and verify per version that reducing allocations smoothed it on real devices.

Spread Occasional Heavy Work Across Frames

Reduce stutter by spreading occasional heavy operations across multiple frames instead of doing them all at once, so no single frame spikes. A periodic heavy operation done in one frame causes a hitch, spreading it smooths the frame time.

Bugnet captures frame time data, so you can see the periodic spikes and their pattern, helping you identify the occasional heavy operations to spread across frames to reduce the hitches.

Move Blocking Operations Off the Main Thread

Reduce stutter by moving blocking operations (loading, I/O, synchronous work) off the main thread, since a main-thread hitch causes a frame to take too long. Doing this work asynchronously keeps the main thread responsive and frames smooth.

Bugnet captures the hitches and freezes from main-thread blocking (with context), so you can see when blocking operations cause stutter and move them off the main thread, then verify per version the stutter reduced.

Reduce stutter by cutting per-frame memory allocations (the leading cause of GC stutter), spreading occasional heavy work across frames, and moving blocking operations off the main thread.