One common method to reduce garbage collection pauses is to...

One common method to reduce garbage collection pauses is to...

• A. Increase runtime allocations.
• B. Use object pools to reuse objects and minimize allocations.
• C. Rely entirely on automatic GC with no optimization.
• D. Reduce texture quality to save memory.

Answer: (B)

Reducing garbage collection pauses comes from lowering how often the program creates short-lived objects. When many new objects are created and quickly become unused, the garbage collector has to run more often, pausing the game to reclaim memory. Using object pools to reuse objects means you create them once and reuse them instead of repeatedly allocating and freeing, which dramatically cuts the number of allocations the GC has to handle. With fewer allocations, the garbage collector runs less frequently and for shorter stretches, improving smoothness and responsiveness. The other options either increase allocation pressure, rely on the GC without any optimization, or address memory usage in a way that doesn’t directly reduce allocation churn, so they’re not as effective as pooling.

Reducing garbage collection pauses comes from lowering how often the program creates short-lived objects. When many new objects are created and quickly become unused, the garbage collector has to run more often, pausing the game to reclaim memory. Using object pools to reuse objects means you create them once and reuse them instead of repeatedly allocating and freeing, which dramatically cuts the number of allocations the GC has to handle. With fewer allocations, the garbage collector runs less frequently and for shorter stretches, improving smoothness and responsiveness. The other options either increase allocation pressure, rely on the GC without any optimization, or address memory usage in a way that doesn’t directly reduce allocation churn, so they’re not as effective as pooling.