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:
- Balance index (0–100) — used only for CPU vs GPU pairing math so resolution/settings still flip limiters sensibly.
- Throughput index — GPU relative to RTX 3060 = 100; CPU relative to Ryzen 5 5600 = 100. Used for upgrade % gains. FPS uses GPU throughput when GPU-limited and a separate CPU scale when CPU-limited.
Data: manufacturer specs + our Relative Gaming Index (RGI).
How editorial relative ordering is produced
- Start from manufacturer product facts (cores/threads/clocks/TDP for CPUs; VRAM/bus/TDP for GPUs).
- Place each part on the throughput ladder with fixed anchors: RTX 3060 = 100 (GPU) and Ryzen 5 5600 = 100 (CPU gaming).
- Keep within-family order strict (e.g. 4060 < 4070 < 4080 < 4090; 7600 < 7800 XT < 7900 XTX).
- 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.
- Automated tests in CI reject catalog changes that break those band checks or tier order.
- 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) / settingsWhat 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
- CPU-side gaps above ~15% are flagged as problems for gaming (warning/red).
- GPU-bound gaming is always framed as healthy (green) at any gap size.
- The severity bands below apply to CPU-bound results:
- 0–10%: Excellent balance for the selected settings.
- 10–20%: Mild gap — usually fine; watch CPU-bound cases at high refresh.
- 20–30%: Noticeable — for CPU-bound results, upgrade the CPU if you need more FPS.
- 30%+: Large CPU-side gap — the CPU is clearly setting the ceiling.
Upgrade rules
- At least ~25% higher on the throughput index.
- At 1440p and above (or when the current card has 12GB+), never suggest less VRAM.
- Prefer currently sold (“new-market”) parts over discontinued used-market cards when competitive.
- Include a competitive AMD option when one fits the gain band.
Data we use
- AMD product specifications — Cores, threads, boost clocks, TDP, socket, and product family for Ryzen CPUs. Reference
- Intel product specifications (ARK) — Cores, threads, boost clocks, TDP, socket, and product family for Core and Core Ultra CPUs. Reference
- NVIDIA GeForce product specifications — VRAM, TDP, bus, and product family for GeForce GPUs (board-partner SKUs may vary). Reference
- pcbottlenecktest Relative Gaming Index (RGI) — Our processed pairing and throughput scores: manufacturer specs plus editorial relative ordering, anchored at RTX 3060 = 100 (GPU) and Ryzen 5 5600 = 100 (CPU gaming). Estimates only — see methodology for how scores are built and checked. Reference