Genre guides6 min read

What Is a Bottleneck in a Gaming PC, and How to Spot One

A bottleneck is the part that sets the pace for the whole PC. This guide explains how one forms, why there is always one, which symptoms point to the CPU, GPU, memory, disk or network, and when fixing it is not worth the money.

Render of the William's XASTER XL patrol ship seen from below against a dark sky
Render of our own ships, made in Blender. Not an in-game capture.

In short

  • A bottleneck is the slowest link in the chain that produces every frame: the game runs at the speed of that link, however powerful the others are.
  • There is always a bottleneck. It is not a defect of your PC: what matters is which one it is, whether it sits where you want it and whether changing it pays off.
  • A GPU that does not reach 100 % usage in a demanding game is the most reliable hint that something else is limiting it, usually one CPU thread, but also possibly memory, storage, the network or a limit in the engine itself.
  • You find it by changing one setting at a time and watching what moves: if lowering the resolution does not raise your frame rate, the bottleneck is not the GPU.

A bottleneck is the part, or the process, that sets the pace for your whole PC while you play. Every frame you see has gone through a chain (CPU, GPU, display), and the chain moves at the speed of its slowest link. If your graphics card could draw 150 frames per second but the CPU can only prepare 90, you see 90, and the graphics card spends the rest of its time waiting.

The idea is simple and the consequences are expensive: many people replace the GPU to gain frames when the limit was somewhere else. This guide explains how a bottleneck forms, what gives it away and when it is worth acting.

To produce one frame, the CPU does the logic: it simulates the world, moves the characters, computes physics, processes what arrives from the network and prepares the draw commands. The GPU receives those commands and paints the pixels. Then the display shows the result. In modern engines these stages overlap, like an assembly line: while the GPU paints frame 100, the CPU is already preparing frame 101.

CPUprepares the frame: 12 msGPUdraws: 8 ms, waits 4 msDisplay1 frame / 12 msRound numbers, not a measurement: the CPU sets the pace

The figure in the diagram is not a measurement of any game: it is arithmetic. If the CPU needs 12 ms per frame, the ceiling is 1000 / 12 ≈ 83 frames per second, whatever the GPU can do. The link between milliseconds and frames per second is covered in frames per second and milliseconds.

There is always a bottleneck

In any PC, something limits you at every moment. Fix the CPU and the GPU limits you; fix the GPU and memory or the display limits you. That is why “no bottleneck” is not a realistic goal. Three questions are useful instead:

  1. Which one is it today? It depends on the game, the resolution and the settings.
  2. Is it where I want it? In a demanding game the ideal is for the GPU to be the limit at a high frame rate, because that is the limit you can move by lowering quality. A CPU limit moves with much less room.
  3. Is it worth changing? If you already get the frames you need, there is nothing to fix.

The possible bottlenecks

Link When it limits What you notice
GPU High resolutions, shadows, global illumination, volumetric effects GPU usage near 100 %; frames rise when you lower the resolution
CPU (one thread) Many characters, heavy simulation, many draw commands GPU below 100 %; one CPU core near 100 %; frames do not change when you lower the resolution
CPU (all threads) Processors with few cores, lots of background activity All cores high; stutter when other programs open
System RAM Low capacity, a single module, memory profile not enabled Stutter when loading zones; minimum frame rates far below the average
VRAM Textures above the card’s memory Sudden drops and stutter even when GPU usage looks normal
Storage Worlds that load on the fly, hard drive or nearly full SSD Stutter when turning the camera or crossing into a new zone
Network High latency, packet loss Characters that teleport, actions that answer late; frame rate is fine
Display and settings V-Sync, frame limiter, refresh rate Frame rate pinned to a fixed number such as 60 or 144
Cooling and power High temperatures, power limits Performance drops a few minutes into a session

The network deserves its own note: ping does not change your frame rate, but it changes what you feel. That is covered in ping, latency and servers in an MMO.

Symptom, likely cause, what to try

Symptom Most likely cause First test
GPU at 95-100 %, low frame rate GPU limit Lower the internal resolution or enable an upscaler
GPU at 50-70 %, one CPU core at 100 % Single-thread CPU limit Lower population, draw distance and shadows; do not lower the resolution
Frame rate stuck at 60 or 144 with a low GPU V-Sync or a limiter is on Check the frame limiter and vertical sync
Good average, frequent stutter Poor 1 % lows: memory, storage or VRAM Check dual-channel RAM, the SSD and the texture setting
Starts smooth, degrades over time Temperature or power limit Check temperatures and clocks after 10 minutes
Good frame rate, late response Network latency or display-chain latency Measure ping and check Reflex or the low-latency mode

For the most common case, a GPU that does not reach its maximum, continue with why your GPU is not at 100 %. To tell the two big limits apart with a five-minute test, see CPU-bound versus GPU-bound.

How to check without guessing

  1. Pick a demanding, repeatable scene, such as an area with many characters, and stand in the same spot every time.
  2. Watch per-core usage, not just the total. A 16-core, 32-thread processor with one thread at 100 % reports 3 % total usage. The total lies.
  3. Change one thing. Drop the resolution one step. If the frame rate rises, the GPU was the limit. If it does not, it was not.
  4. Measure milliseconds, not only frames. Free tools such as PresentMon or CapFrameX record the time of every frame and let you compute averages and minimums. The full guide is how to measure your PC’s performance.

When fixing it is not worth it

A bottleneck is a problem only if the result is not enough for you. If you play at 144 frames per second on a 144 Hz display with the CPU as the limit, there is nothing to improve. If your display is 60 Hz, any PC that holds a steady 60 frames is enough, and spending more only moves the bottleneck somewhere else. Fixing a limit pays off when it stops you reaching what you can already see.

Bottlenecks in persistent-world games

Online games with many players, a lot of fauna and a lot of building tend to be limited by the CPU rather than the GPU: many entities have to be simulated, animated and drawn at once. That is the case for a persistent-world survival MMO such as COLONIZED, which is built with Unreal Engine 5. Closed alpha applications are open and the first wave is planned for winter 2026-2027; it cannot be played yet, and we have not published system requirements. What we have measured in the development build, on video memory and cloud cost, is in our guide to optimizing Unreal Engine 5 games. The reason for this tendency is in why MMOs and survival games depend on the CPU.

To choose hardware with all this in mind, the buying guide is the best PC for MMO and survival games in 2026-2027.

Questions and answers

What is a bottleneck in a PC?

It is the part or process that limits the speed of the whole system. Every frame goes through the CPU, the GPU and the display in a chain, and the slowest link sets the pace. If the CPU needs 12 ms to prepare a frame and the GPU needs 8 ms to draw it, the game runs at about 83 frames per second and the GPU waits.

Is having a bottleneck bad?

Not necessarily. Something always limits you; what matters is whether you get the frame rate and smoothness you want. A balanced PC changes its bottleneck depending on the game, the resolution and the settings, and that is normal.

How do I know if my CPU is holding back my GPU?

Check GPU usage in a demanding game. If it is well below 100 % and one CPU core is close to 100 %, the CPU is the suspect. The definitive test is to lower the resolution: if the frame rate barely rises, the GPU was not the limit.

Does a new graphics card fix a bottleneck?

Only if the limit is the GPU. If the limit is the CPU, a faster graphics card does not raise your frame rate and the money goes to the wrong place. Identify the bottleneck first, then decide what to replace.

Sources

Third-party figures link to their source. The date is the publication date or, when there is none, the day we checked the page.

  1. PresentMon: capture and analysis of graphics performance · Intel (GameTechDev, GitHub) · 2026-10-22
  2. CapFrameX: capture, analyze and compare game performance · CapFrameX (GitHub) · 2026-10-22