AMD Ryzen 5 7500F + Intel Arc A380

Processor

AMD Ryzen 5 7500F

26,716
CPU Mark
Faster than 92% of 1,255
47.56 % BOTTLENECK
One part is holding you back
Graphics card

Intel Arc A380

6,314
G3D Mark
Faster than 54% of 268
Limiting part

The AMD Ryzen 5 7500F paired with the Intel Arc A380 produces a 47.56% bottleneck. The GPU is the limit, so it finishes its share of each frame last and the other component waits. A gap this size is worth planning an upgrade around.

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 45.3% bottleneck · GPU-limited
Largest imbalance 7680x4620 89.8% bottleneck · GPU-limited

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

1280x720 45.3%
GPU-limited
1366x768 45.8%
GPU-limited
1600x900 46.2%
GPU-limited
1920x1080 your setting 47.6%
GPU-limited
2560x1440 48.5%
GPU-limited
3840x2160 58.3%
GPU-limited
5120x2880 67.3%
GPU-limited
7680x4620 89.8%
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 AMD Ryzen 5 7500F Faster than 92% of CPUs listed · #103 of 1,255
Graphics card Intel Arc A380 Faster than 54% of GPUs listed · #122 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 Intel Arc A380

Other graphics cards with the AMD Ryzen 5 7500F

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