Why Your Frame Rate Is Lying to You
Average FPS is the number everyone quotes and the number that tells you the least. Two systems can post the same average and feel completely different to play, because the average hides exactly the thing that matters: consistency.
The number that actually matters
Frame time — how long each individual frame takes to render — is the metric that maps to how a game actually feels. A run of frames delivered evenly at 90fps will feel smoother than a run averaging 100fps with regular spikes down to 60. Your eyes and hands notice the spikes; they don't notice the average.
This is why two rigs with near-identical benchmark averages can feel worlds apart in a fast-paced match. One is holding a steady frame time. The other is lurching between fast and slow frames and calling it even, on average.
What actually causes the stutter
In most builds I look at, inconsistent frame times trace back to one of three places: a CPU bottleneck that only shows up under heavy scene load, background processes competing for resources at the worst moment, or storage that's slow enough to cause texture pop-in mid-fight. None of these show up clearly in a simple average FPS counter.
"A steady 90 will always beat a spiky 120 — your reflexes are timing against the dips, not the peaks."
What to actually look at
If you want a real read on performance, look at 1% and 0.1% low frame rates alongside the average, and watch a frame-time graph during actual play rather than a synthetic benchmark. That combination tells you where the experience actually breaks down — which is the only number worth optimizing around.