Skip to content
pcbottlenecktest
Menu
pcbottlenecktest

Methodology

Last updated 2026-10-10. Editor: pcbottlenecktest Editorial Team.

What we estimate

We compare relative CPU and GPU indexes, then adjust for resolution, graphics settings, refresh rate, RAM, storage and use case. Outputs are estimates, not measured FPS from a specific title. Rough FPS ranges use GPU throughput when you are GPU-limited and a separate CPU frame ceiling when you are CPU-limited.

Relative Gaming Index (RGI)

RGI has two layers:

Data: manufacturer specs + our Relative Gaming Index (RGI).

How editorial relative ordering is produced

  1. Start from manufacturer product facts (cores/threads/clocks/TDP for CPUs; VRAM/bus/TDP for GPUs).
  2. Place each part on the throughput ladder with fixed anchors: RTX 3060 = 100 (GPU) and Ryzen 5 5600 = 100 (CPU gaming).
  3. Keep within-family order strict (e.g. 4060 < 4070 < 4080 < 4090; 7600 < 7800 XT < 7900 XTX).
  4. Set cross-brand steps so common upgrades land in published review bands — for example 3060→4070 about +60–90%, 3060→4070 Ti Super about +100–140%, 6700 XT→7800 XT about +25–50%, and 4090→5090 about +25–30%. These are sanity checks on relative spacing, not copied score tables.
  5. Automated tests in CI reject catalog changes that break those band checks or tier order.
  6. Spot-check popular pairings (e.g. 5600+3060, 7600+4070, 5800X3D+4090, 9800X3D+5090) against the direction of published reviews — GPU-bound where expected, CPU-bound where the GPU clearly outclasses the CPU at 1080p, and 4090→5090 about +25–30% when the GPU is the FPS cap — without copying numeric score tables.

RGI scores are editorial estimates, not republished benchmark tables from third-party sites. Full process notes also live on the data sources page.

Formula (summary)

cpuScore = (balanceIndex / useCaseCpuDemand) × refreshLoad × storageFactor
gpuScore = (balanceIndex / useCaseGpuDemand × ramFactor) / (resolutionLoad × settingsLoad)
balance  = cpuScore / gpuScore
→ CPU limiter if balance < 1, GPU limiter if balance > 1
upgradeGain% = (newThroughput − oldThroughput) / oldThroughput
fpsEst ≈ min(gpuThroughput × gpuFpsFactor, cpuThroughput × cpuFpsFactor) / settings

What the big percentage means

For GPU-bound gaming it is CPU headroom unused — how much CPU capability sits idle while the GPU is fully loaded. That is healthy, not a fault. For CPU-bound results it is GPU headroom unused.

Thresholds and framing

Upgrade rules

Data we use

Data sources & update log