Why bottleneck calculators disagree — and which number to trust

Run the same CPU and GPU through three different bottleneck calculators and you'll often get three different answers — 4%, 11%, 23%. That's not a glitch. It's the whole problem with the category.

The reason is simple: a "bottleneck percentage" isn't a measured fact like a temperature reading. It's the output of a formula, and every site uses a different one. Different benchmark sources, different weightings, different assumptions about resolution — all hidden behind a single confident number and a buy-now button.

Aren't bottleneck calculators just snake oil?

It's a fair charge. Spend five minutes on r/buildapc or the Tom's Hardware forums and you'll see the same verdict over and over: bottleneck calculators are "snake oil," "complete garbage," numbers conjured from nowhere. The experts saying it aren't wrong about most of these tools. It's worth taking each complaint seriously, because every one has a legitimate core — and it's exactly what we built this calculator to answer.

• "Same parts, a different number every time." People report feeding in identical hardware and getting 2%, then 18%, then 40% on different days or different sites. That's what happens when a tool quietly recalibrates on user-submitted data or hides which assumptions it used. Our number is deterministic: the same inputs always produce the same output, from a fixed dataset and the formula you can read below. No drift, no mystery.
• "It's one number for an infinite-variable problem." The strongest objection — and it's correct. A real bottleneck depends on the game, the settings and the resolution, so any single universal percentage is hiding all of that. That's why we never give one: every result is tied to a resolution, you can attach a specific game, and we show a confidence range instead of a false-precise point. We try to model the variance the critics say is unmodelable, rather than averaging it into a meaningless figure.
• "They only exist to scare you into buying." Many do — when the business model is affiliate clicks, the incentive is to report an alarming number and steer you to an expensive part (XDA documents calculators recommending absurd upgrades). We do the opposite: we only suggest an upgrade when it would actually add frames at your resolution, and when your build is already balanced we say so and recommend nothing.

So the honest answer is that most bottleneck calculators have earned the skepticism. The fix isn't a better-hidden formula — it's no hidden formula at all. Everything below is exactly how we reach our number, in the open, so you can check it instead of trusting it.

What does the number actually measure?

At its core, a bottleneck percentage estimates how far apart your CPU and GPU are in capability for a given workload. If one can do far more than the other can keep up with, the stronger part sits partly idle, and that gap, expressed as a percentage, is the "bottleneck."

The trouble is that "capability" depends entirely on the game, the resolution, and the settings. Change any of those and the honest answer changes too. There is no single true bottleneck number for a pair of parts — only a bottleneck for a specific situation. Any calculator that hands you one universal percentage has quietly thrown that context away.

Why do three sites give three answers?

• Different data. One site averages a dozen real game benchmarks; another uses a synthetic score like a single 3DMark run. Same parts, different underlying numbers, so different gaps.
• Different resolution handling. A pair that's CPU-bound at 1080p can be GPU-bound at 4K. A calculator that ignores resolution is averaging two opposite situations into one meaningless figure.
• Different math. Some divide the gap by the weaker part, some by the stronger, some by the average. That choice alone can double or halve the headline number from the exact same inputs.

Here's how big that last one is. Say a benchmark puts your GPU at 100 and your CPU at 80 — a 20-point gap. Divide that gap by the stronger part and you get a 20% bottleneck; divide it by the weaker part and you get 25%; divide by the average and you get about 22%. Same two parts, same data, three "official" percentages, purely because the sites picked different denominators.

None of these are necessarily "wrong" — they're just different assumptions. The problem is that almost no site tells you which assumptions it made, so you can't judge whether its number applies to your games at your resolution.

Does resolution really change the answer?

More than almost anything else. The CPU does roughly the same work per frame no matter the resolution — it prepares the game state, the physics, the draw calls. The GPU's job, though, scales with pixels. 1080p is about 2.1 million pixels per frame; 4K is about 8.3 million, four times the load on the same graphics card (build-gaming-computers.com).

So the same CPU and GPU can be CPU-limited at 1080p — the graphics card finishes early and waits — and fully GPU-limited at 4K, where the card is the bottleneck and the CPU coasts. Being GPU-bound at high resolution isn't a flaw to fix; it means you're getting full use of your graphics card. A calculator that reports one number for "your build" without asking your resolution is, by definition, guessing at which situation you're in.

Here's our formula — in the open

We hold ourselves to the same standard, so here's exactly how we get our number. We score every CPU and GPU from real benchmark data on a 0–100 scale, then:

The resolution weight is the honest part most calculators skip: it's high at 1080p (the CPU matters most) and low at 4K (the GPU carries the load). Take one real build — a Ryzen 5 7600 (we score it 46) and an RTX 4070 (69), a gap of about 33% — and apply each resolution's weight:

Same two parts, same data, and the honest answer ranges from 18.4% to 6.7% depending only on the resolution you play at. You can punch this exact build into our bottleneck calculator and reproduce every figure — the full weight table lives in our methodology.

Which number should you trust?

Trust the one that shows its work — which is exactly what we just did. A trustworthy estimate tells you which component is the limiter, at what resolution, using what data, and admits how uncertain it is with a ± range. That's why we attach a confidence band to every result. We'd rather give you an honest range than a precise-looking lie.

It also helps to know what a healthy number looks like. Every real build has some imbalance; under about 15% is balanced, and you shouldn't spend money chasing a perfect zero that doesn't exist. If you're still getting your head around the basics, start with what a bottleneck actually is, or see where your parts land on the GPU hierarchy. So when two calculators disagree, don't ask which number is bigger. Ask which one will show you how it got there.