Balancing monitoring sampling rates against system overhead
Looking at Disk Report 2026-015, I used FPS Monitor and noticed the frame time graph looked like a sawtooth. I dug into the AIDA64 sensor panel and found the controller temp staying between 57℃ - 62℃, with write bandwidth peaking at 3.5GB/s - 4.1GB/s. I tried setting the sampling interval to 1s, but the software itself started eating too much CPU, making the game even laggier. Once I bumped it to 2s, CPU overhead dropped by 12%. RTSS then confirmed the frame curve had finally flattened out, and the tearing was way less noticeable. However, because of the game's streaming engine, you'll still get those brief hitches when flying at max speed. It's a known flaw in the current build.
