1% Lows Explained: Why Average FPS Lies to You
Two PCs both average 120 FPS. One feels buttery; the other stutters every few seconds. The difference is invisible in the average — and obvious in the 1% lows.
What 1% Lows Actually Are
Frame times vary constantly during gameplay. If you sort every frame in a benchmark run from slowest to fastest, the 1% low is the average frame rate of the slowest 1% of frames. (Some tools report the 1st percentile frame time instead — same idea, inverted units.)
Example: 120 FPS average with 1% lows of 110 = consistently smooth. 120 FPS average with 1% lows of 45 = frequent visible hitches, even though the "headline" number looks great.
Why Averages Mislead: The Science
This isn't just enthusiast folklore — it's peer-reviewed:
- Klein et al. (ACM CHI 2023) showed that high-percentile frame-time models predict perceived smoothness better than mean-based models, cutting prediction error by up to ~20%.
- Liu et al. (ACM CHI 2023) found the 95% frame-rate floor effectively predicts player quality of experience across games, where average FPS does not.
- Xu & Claypool (ACM MMSys 2024) showed tail metrics like frame-time standard deviation predict player experience with R² ≈ 0.92, while simple averages miss the stutter players actually feel.
The consistent finding: humans notice the bad moments, not the average. Averages hide exactly what matters.
CPU Bottlenecks Live in the Lows
This is why 1% lows matter for bottleneck analysis specifically. CPU-side problems show up as hitches, not as a uniformly lower frame rate:
- Shader compilation stutter (first-time effects in a new area)
- Asset streaming hitches (open world loading, slow storage)
- Background task spikes (Windows updates, antivirus, browser)
- Draw-call spikes (busy scenes with many characters)
A CPU-limited system often posts a respectable average FPS while its 1% lows crater — which is exactly why our calculator's 10–20% band notes "may see lower 1% lows." The percentage flags the risk; the lows confirm the reality.
How to Measure 1% Lows Yourself
- CapFrameX (free, recommended): detailed frame-time analysis, percentile overlays.
- Intel PresentMon (free, open): the underlying capture technology many tools use.
- NVIDIA FrameView (free): simple overlay with averages and percentiles.
Method: run a repeatable in-game benchmark or a fixed gameplay path for 60+ seconds, with settings you actually play at. Compare runs — single runs are noisy.
What Do Good 1% Lows Look Like?
Rule of thumb: 1% lows within 70–80% of your average FPS feel smooth to most players. A large gap (average 144, lows 60) means something is wrong — usually CPU-side hitches, thermal throttling, or a game-specific issue worth investigating before blaming hardware balance.
Bottom Line
Average FPS is a headline; 1% lows are the review. When evaluating any bottleneck result, ask what happens in the worst 1% of frames — that's the part you'll actually feel.