What a bottleneck index actually measures
At its simplest, a bottleneck index estimates which part sets the pace in a given pairing, at a given resolution, in a given kind of game. It is not a benchmark and not a frame-rate prediction. It is a summary: it takes the relative strength of a CPU and a GPU, weighs them by resolution and workload, and reports which side is more likely to limit performance and by roughly how much.
Three inputs matter most. First, the pairing itself — the CPU's per-core speed and core count against the GPU's rendering power. Second, the resolution — the same pairing can be CPU-limited at 1080p and GPU-limited at 4K, so an index without a resolution attached is meaningless. Third, the workload — competitive games at high refresh rates stress the CPU far more than cinematic single-player games at 4K, so a single number cannot describe both.
A good index also says what it is not measuring: RAM speed and capacity, storage speed, cooling, drivers, and the specific game engine. Those can all change real performance, which is why an index is a starting point for a decision, not the decision itself. Our full method is described in how we calculate bottlenecks, and the background piece the bottleneck index explained covers the basic idea.
How to read the ranges, not the number
An index is most honest when it speaks in ranges. A pairing described as broadly balanced across 1080p, 1440p and 4K tells you more than a single decimal figure, because real performance varies by game, scene, driver and room temperature. Treat any index value as the middle of a range, and ask how wide that range is before you act on it.
Read the index in three steps. First, check the resolution it was calculated for — if it does not match yours, the conclusion may not apply. Second, check the game type — an index weighted toward competitive shooters will look different from one weighted toward open-world games. Third, check the direction: is the CPU or the GPU the likely limit, and does that match what you see when you play? If the index and your own monitoring disagree, trust your monitoring and investigate why.
Small differences are not decisions. If two pairings sit in the same broad range, the cheaper one, the one with more video memory, or the one that fits your power supply is usually the better buy. Only a large, consistent gap across resolutions is a strong reason to change a part.
The questions to ask in the second quarter
The second quarter is a planning quarter. Spring sales are ending, summer sale season is approaching, and new game announcements start to shape what autumn will demand. The useful questions for this period are about direction, not about a single score.
- Has the balance shifted for your resolution? A pairing that was balanced at 1080p may look different once you move to 1440p, and an index read at the wrong resolution will mislead you.
- Are you buying for the games you play now, or the ones coming later? An index describes today's common workloads; upcoming releases may stress the CPU or GPU differently, so treat autumn plans as a separate check.
- What else changed? A driver update, a RAM upgrade or a hotter room can move real performance without moving the index at all. Re-check your own system before blaming the pairing.
- Is the gap worth the money? A modest imbalance that only shows at 1080p high refresh may not justify a new part if you play at 1440p. Match the fix to where you actually play.
If you are weighing a purchase around sale season, the advance guide Steam Summer Sale GPU upgrades shows how to check balance before a discount tempts you into a mismatch.
What an index cannot tell you
An index cannot tell you your exact frame rate, because frame rate depends on the game, the scene, the settings and your system. It cannot tell you whether a specific game will stutter, because stutter often comes from storage, RAM or drivers rather than the CPU-GPU balance. And it cannot tell you what to buy, because price, power supply, case size and monitor all sit outside the calculation.
| Index input | What it tells you | What it cannot tell you |
|---|---|---|
| CPU vs GPU strength | Which part is more likely to set the pace | Your exact frame rate in any game |
| Resolution weighting | How the balance shifts from 1080p to 4K | How a specific game engine behaves |
| Workload type | Whether competitive or cinematic games stress the CPU more | Stutter from RAM, storage or drivers |
| Pairing comparison | Which of two pairings is more balanced | Which is the better buy for your budget |
Use the index to shortlist, then verify with your own use: run your games, watch per-core CPU usage and GPU usage, and check the result at your resolution. If you want the background on sensible ranges, see good bottleneck percentage ranges.
Limitation: this article is an explainer, not an index report. It contains no index scores, rankings or measured results, because those require collected, calibrated data for the period in question. Any index you read should show its inputs and its date; one that does not is not worth acting on.
Frequently asked questions
What is a bottleneck index in simple terms?
It is a summary that estimates which part — CPU or GPU — is more likely to limit performance in a pairing, at a given resolution and game type. It is not a frame-rate prediction and not a benchmark; it is a way to compare pairings at a glance before you dig into the detail.
Why does the same pairing get different index readings?
Because resolution and workload change the answer. The same CPU and GPU can be CPU-limited at 1080p, balanced at 1440p and GPU-limited at 4K, and competitive games stress the CPU more than cinematic games do. An index reading only means something when you know which resolution and workload it was calculated for.
Should I upgrade if the index shows a small imbalance?
Usually not on that evidence alone. Small differences fall inside the normal range of variation between games and scenes, and they may not show at your resolution at all. Upgrade when the imbalance is large, consistent across resolutions you actually use, and visible in your own monitoring while you play.
Does the index account for RAM, cooling and drivers?
No — and that is its main limit. RAM speed and capacity, storage, cooling and drivers can all change real performance without changing the index. That is why an index is a shortlisting tool: use it to narrow choices, then check your own system and the specific games you play before spending money.
How often should an index be updated?
Whenever the inputs change meaningfully: new CPU or GPU launches, major driver or game-engine changes, or a shift in the most-played games. A quarterly rhythm is a reasonable planning cadence, but the date and the inputs of any reading matter more than how recently it was published — an undated index is not a reliable guide.