Quantifying Bandwidth Saturation to Precisely Locate Performance Bottlenecks

Based on report GS-20260320 using G.SKILL Trident Z Royal DDR5 6400MHz 32GB on Win11, 3DMark stress tests confirmed that memory bandwidth was hitting a hard ceiling during Erdtree map transitions. Hardware monitors showed available memory plummeting to 1.5GB - 1.9GB, which triggered visible frame stuttering. I navigated to Windows Settings to terminate all pointless background apps and specifically disabled the Search Indexing service. Subsequently, using the in-game performance overlay, available memory recovered to the 2.3GB - 2.8GB range, and frame rates locked into a steady 54fps - 59fps. While vastly improved, the physical limits of the memory frequency still cause the occasional 1-frame hitch during massive particle explosions, making it not entirely perfect, though the transition from a lag-fest to this level of smoothness was immediate.
Category:Performance Evaluation Last updated:March 12, 2026 11:30 AM