All articles
Performance

Frame Pacing and 1% Lows: Why Average FPS Lies

Why a game running at 120 average FPS can still feel worse than 90 FPS, and how to fix it.

6 min read·March 2, 2026
Frame Pacing and 1% Lows: Why Average FPS Lies

Average FPS hides everything

A 120-FPS average can be made of one frame at 200 FPS, one at 40, repeat. Average looks great, gameplay feels awful. That is bad frame pacing.

What you actually want

  • High 1% low FPS (the slowest 1% of frames).
  • A flat frame-time graph in MSI Afterburner.
  • No spikes above ~30 ms (anything above ~33 ms = visible stutter).

Common pacing killers

  • Slow / single-channel RAM (see RAM and FPS).
  • Background apps stealing CPU time.
  • Shader compilation on first run.
  • Storage I/O on an HDD.
  • VRAM saturation, texture pop, sudden 80 ms spikes.
  • V-Sync mis-configured with G-Sync.

How to measure

Use CapFrameX or the FrameView OSD. Watch the 1% / 0.1% lows, not the average. If 1% is 70% of average, you are smooth. If it is below 50%, the game is stuttering.

Fix order

1. Enable XMP/EXPO and dual-channel RAM.

2. Move the game to NVMe.

3. Cap FPS slightly below your monitor refresh (e.g. 138 on a 144Hz panel) with G-Sync on.

4. Disable resource-hungry overlays.

5. If stutter persists with low GPU usage, you are CPU-bound, see bottleneck checks.

Run your own numbers

Open the free bottleneck calculator or estimate FPS with the FPS calculator.