Intel Core i5-7500 @ 3.40GHz + Radeon RX 6400

Processor

Intel Core i5-7500 @ 3.40GHz

6,029
CPU Mark
Faster than 67% of 1,255
Limiting part
12 % BOTTLENECK
Mild imbalance
Graphics card

Radeon RX 6400

7,741
G3D Mark
Faster than 56% of 268

The Intel Core i5-7500 @ 3.40GHz paired with the Radeon RX 6400 produces a 12% bottleneck. The CPU is the limit, so it finishes its share of each frame last and the other component waits. A gap this size is usually recoverable through resolution and settings rather than new hardware.

Every build has a bottleneck; the question is only whether it sits where you want it. Read the figure alongside the limiting part, because the same percentage means different things at 1080p and at 4K.

Bottleneck by resolution

Raising resolution shifts load from the CPU to the GPU, so the balance of this pairing changes with the display it drives. Note this measures imbalance, not speed: the lowest figure is usually the lowest resolution, which is not the one to play at. Read it alongside the limiting part.

Smallest imbalance 1280x720 11.2% bottleneck · CPU-limited
Largest imbalance 7680x4620 22.2% bottleneck · GPU-limited

On this chart a longer bar is worse: it measures imbalance, not speed.

1280x720 11.2%
CPU-limited
1366x768 11.3%
CPU-limited
1600x900 11.5%
CPU-limited
1920x1080 11.8%
CPU-limited
2560x1440 your setting 12.0%
CPU-limited
3840x2160 14.5%
GPU-limited
5120x2880 16.7%
GPU-limited
7680x4620 22.2%
GPU-limited

How these parts rank

Position within the 1,255 processors and 268 graphics cards in our database, by the same benchmark scores this calculator runs on.

Processor Intel Core i5-7500 @ 3.40GHz Faster than 67% of CPUs listed · #416 of 1,255
Graphics card Radeon RX 6400 Faster than 56% of GPUs listed · #119 of 268

Upgrade options

ASUS ROG Strix NVIDIA GeForce RTX™ 4070 Ti

$1050 Check price

AMD Ryzen 7 5800X

Intel Core i7-13700K

Related pairings

Other processors with the Radeon RX 6400

Other graphics cards with the Intel Core i5-7500 @ 3.40GHz

Try a different pairing

Swap either component and see how the balance moves. Changing the resolution alone often matters more than changing a part.

Run another build

Similar calculations