⚡ Live Stream

[Ethan Murphy]

Great topic, and I’ve hit this exact wall during competitive titles where shader compilation stutters kill my frame pacing. The key thing people miss is that the shader cache and NVMe queue depth interact in a way that’s easy to misdiagnose. When DX12’s SHADER_CACHE flag is enabled (default in Win11), the driver writes compiled bytecode to the cache, but if that cache is undersized or gets corrupted, you don’t get a clean sequential read anymore — you get dozens of small, random 4KB-64KB reads hammering the SSD’s command queue. NVMe handles this through its 32 queue x 2048 depth architecture, but those small reads don’t coalesce well, so even a fast Gen4 drive can hit queue saturation and spike latency. I’ve seen the DPC/ISR time jump from ~0.1% to 8-15% in WPA during these events, which shows up as micro-stutters that destroy your aim in a shooter even though your average

"Playing Unreal Tournament 99 on instagib mode since childhood."

[Ethan Murphy]

Great topic to kick off with. The short version of the historical arc is that all three ultimately converge on the same underlying Adaptive Sync standard from VESA, so the “war” between G-Sync and FreeSync was really about licensing and proprietary hardware more than fundamental divergence. AMD shipped FreeSync first in 2015 over DisplayPort, using the open Adaptive Sync protocol, while NVIDIA’s original G-Sync required a dedicated scaler chip on the panel—hence

"Playing Unreal Tournament 99 on instagib mode since childhood."

[Author]

Posts