Last updated: October 2, 2026

Quick answer: Average frames per second (FPS) measures overall rendering throughput, while the 1 percent low metric measures the worst 1% of frame delivery times converted back to an FPS figure. A system delivering high average FPS can still stutter severely if its 1 percent low dips significantly below the monitor refresh rate.

msi Gaming RTX 5080 16G SUPRIM Liquid SOC Graphics Card (16GB GDDR7

Short answer: The comparison between average FPS vs 1 percent low defines the boundary between perceived speed and actual smoothness in gaming. Average FPS divides total rendered frames by total benchmark time, hiding brief pauses. The 1 percent low isolates frame time spikes caused by CPU engine stalls, asset streaming delays, memory bandwidth constraints, or thermal throttling. In October 2026, reading modern GPU Benchmarks requires tracking both figures to prevent buying a GPU or CPU that produces micro-stutters during heavy combat or open-world traversal.

What Is Average FPS Vs 1 Percent Low?

Average FPS represents the arithmetic mean of all frames generated by a graphics card over an entire test sequence. It answers how many frames the system renders per second on paper. The 1 percent low metric targets frame pacing by calculating the 99th percentile of longest frame delivery times, then converting that duration into frames per second. While average FPS reflects gross compute capability, the 1 percent low metric reflects minimum rendering stability.

A benchmark reporting 144 average FPS sounds ideal for a 144 Hz display. However, if that same run records a 1 percent low of 38 FPS, the player will perceive erratic hitches, input lag spikes, and judder. The metric distinguishes clean, uniform frame output from bursty, inconsistent output.

Why Average FPS Vs 1 Percent Low Matters

Evaluating graphics cards, processors, and system memory solely on average FPS leads to flawed purchasing decisions. Frame time variance dictates the tactile feel of mouse tracking and visual persistence. When a single frame takes 50 milliseconds to deliver instead of the normal 6.9 milliseconds expected at 144 FPS, the display holds a stale image for several refresh cycles.

Modern game engines stream assets dynamically into video memory (VRAM) and system RAM. If a graphics card exhausts its onboard VRAM buffer, it transfers textures across the PCIe bus, causing severe frame drops. Average FPS might barely register this hiccup over a three-minute benchmark run, dropping from 120 FPS to 117 FPS. Conversely, the 1 percent low metric captures the drop immediately, exposing the hardware bottleneck. Understanding these metrics prevents buyers from overspending on raw GPU compute when a CPU or system memory upgrade would yield smoother motion clarity.

How Average FPS Vs 1 Percent Low Works

Hardware testing software records the precise rendering time of every individual frame in milliseconds (ms). An examination of internal pipeline mechanics shows how these calculations occur.

Frame Generation and Milliseconds

A monitor does not receive frames in aggregate buckets; it refreshes at fixed intervals. At a constant 60 FPS, each frame takes exactly 16.67 ms. At 144 FPS, each frame requires 6.94 ms. Average FPS calculates total frames divided by total seconds, entirely ignoring whether individual frames took 5 ms or 45 ms. Frame time tracking logs the duration of every frame drawn from start to display presentation.

The 99th Percentile Calculation

To calculate the 1 percent low, benchmark utilities like CapFrameX, PresentMon, or MSI Afterburner sort all logged frame times from fastest to slowest. The software identifies the slowest 1% of frames (the 99th percentile frame times). The average duration of these outlier frames is converted to an FPS equivalent using the formula: FPS = 1000 / Frame Time (ms). If the slowest 1% of frames average 33.3 ms, the 1 percent low displays as 30 FPS.

Hardware Root Causes for Low Percentiles

Disparities between average FPS and 1 percent low arise from distinct hardware constraints:

  • CPU draw calls: When a game engine prepares geometry and lighting states, the CPU directs the GPU. If the CPU lacks single-thread speed or L3 cache capacity, draw calls stall, collapsing 1 percent lows while the GPU idles.
  • VRAM saturation: When texture data exceeds physical GPU memory, data spills into system RAM. The PCIe link bandwidth limits transfers, creating sudden 30-80 ms frame spikes.
  • Memory latency: Sub-optimal memory timings, single-channel configurations, or high memory latency impede CPU-to-RAM communications during physics calculations and asset loading.
  • Thermal throttling: If a CPU or GPU core hits thermal safety trip points, internal clocks downclock aggressively for fractions of a second, causing sharp micro-stutters. Maintaining a safe CPU temperature while gaming keeps clock frequencies stable and prevents percentiles from collapsing.

Quick Comparison

Metric What It Measures Primary Hardware Cause Gameplay Impact
Average FPS Total throughput across entire run GPU rasterization and compute cores Sets theoretical maximum refresh rate target
1 Percent Low Worst 1% frame times converted to FPS CPU cache, RAM bandwidth, VRAM capacity Determines presence of hitches and micro-stutter
0.1 Percent Low Worst 0.1% extreme outlier frame times Storage I/O reads, thermal drops, background OS tasks Manifests as complete visual freezes or major lag spikes
Frame Time Variance Delta between consecutive frame durations Display sync misalignments, driver scheduling Causes visible jitter even when raw FPS is high

What to Look For When Buying

When reviewing benchmark charts to choose components, balance average throughput against low-percentile consistency:

  • Target a 70% ratio: Ensure a component’s 1 percent low is at least 70% of its average FPS in demanding titles. If average FPS is 100, the 1 percent low should ideally stay above 70 FPS.
  • Check VRAM thresholds: Modern titles with ray tracing or ultra textures require sufficient dedicated video memory. Selecting GPUs with sufficient VRAM buffers preserves 1 percent lows at high resolutions.
  • Evaluate CPU cache size: CPUs with substantial L3 cache architectures significantly raise 1 percent low metrics by reducing memory access penalties. When planning an upgrade, consider platforms with high gaming cache, such as evaluating best Ryzen 5 3600 upgrades to stabilize system frame delivery.
  • Match display refresh floor: Ensure the 1 percent low remains above the Variable Refresh Rate (VRR) or FreeSync lower bound (typically 40-48 Hz) to avoid sudden tearing or loss of adaptive sync smoothing.

Common Mistakes to Avoid

Relying purely on marketing metrics leads to several common testing and hardware errors:

  • Assuming high average equals smooth motion: A card scoring 200 average FPS with 40 FPS 1 percent lows feels noticeably worse to play than a system scoring 120 average FPS with 105 FPS 1 percent lows.
  • Blaming the GPU for all frame drops: While GPUs control average frame generation at 1440p and 4K, sudden percentile drops are frequently caused by CPU bottlenecks, background Windows processes, or slow system RAM. Check diagnostic software like a cpu temperature monitor windows 11 tool to isolate hardware behavior.
  • Confusing 1 percent low with minimum FPS: Minimum FPS reflects a single worst frame rendered in the entire test run, which can be an anomaly like a menu transition or level load. The 1 percent low is a mathematically rigorous percentile metric that filters out single-frame errors.
  • Ignoring memory configuration: Running DDR4 or DDR5 in single-channel mode drastically slashes 1 percent low performance by halving memory bandwidth, even if average FPS only drops by 10-15%.
  • Relying on built-in game benchmarks: Many built-in benchmarks showcase camera fly-throughs without combat, physics, or asset streaming. These scenarios report inflated 1 percent lows that do not match live, unscripted gameplay.

Explore our broader performance benchmarking analyses and platform optimization guides:

Why You Should Trust PCGearWiki

PCGearWiki focuses on transparent hardware architecture analysis and empirical performance metrics. We analyze documented hardware specifications, verified engineering documentation, and established percentile capture methods to clarify how components interact. Readers can learn more about our review standards and data practices by reviewing How We Evaluate Products. We do not inflate synthetic numbers, claim undocumented lab tests, or prioritize marketing claims over measurable frame delivery characteristics.

Final Thoughts

When analyzing PC hardware performance, average FPS defines capacity, but the 1 percent low metric dictates playability. Prioritize balanced systems that pair capable graphics silicon with robust CPU cache, dual-channel high-speed memory, and sufficient VRAM capacity. Maintaining steady, tightly clustered frame times eliminates perceptible stutter and delivers an authentically smooth gaming experience.

Frequently Asked Questions

What is a good 1 percent low FPS?

A good 1 percent low metric remains within 70% to 80% of the average FPS figure. For competitive shooters played on high-refresh displays, the 1 percent low should ideally stay above the monitor’s base Variable Refresh Rate floor, typically 60 to 120 FPS, to eliminate perceived judder during intense rendering scenes.

Does CPU or GPU affect 1 percent low more?

While the GPU establishes raw graphical throughput, the CPU and memory subsystem heavily influence 1 percent lows. Asset streaming, physics calculations, game engine updates, and draw call scheduling all rely on CPU speed and cache capacity. Weak CPUs or slow memory configurations frequently produce severe 1 percent low drops while the GPU sits underutilized.

How is 1 percent low different from 0.1 percent low?

The 1 percent low isolates the slowest 1% of frame delivery times, representing noticeable micro-stutter. The 0.1 percent low represents the slowest single frame out of every 1,000 frames rendered. The 0.1 percent metric captures extreme edge cases like disk reading stalls, thermal protection drops, or sudden asset loading freezes rather than continuous gameplay pacing.

Can high average FPS still feel choppy?

Yes. A system running at 150 average FPS will feel choppy if frame pacing is irregular. If 140 frames render in 4 ms each and the remaining 10 frames each take 45 ms, the player experiences sudden, repeated micro-freezes. Consistent frame times matter far more to perceived smoothness than high average throughput.