CPU_VS_GPU / 2026-09-11
AMD Ryzen 5 3600vsAMD RX 6800
Complete bottleneck analysis at 1080p, 1440p, Ultrawide (UWQHD/SUWQHD), and 4K with estimated FPS for popular games.
6%
PERFECTLY BALANCED BUILD
Your CPU (Ryzen 5 3600) and GPU (RX 6800) are an exceptionally balanced match for gaming at 2560x1440. No realistic component swap would meaningfully improve this build.
Load estimated by the model, not measured on your PC.
- PROCESSORAMD Ryzen 5 3600
- GRAPHICSAMD RX 6800
- MEMORY16GB DDR4/DDR5
- RESOLUTION2560x1440
Average across the demanding titles at 2560x1440.
Average across the competitive titles, where the processor leads.
What the build draws (465 W) plus headroom.
DEEP-DIVE ANALYSIS
GENERATED BY THE ENGINEPairing the AMD Ryzen 5 3600 (52/100 on our gaming index) with the AMD RX 6800 (34/100) raises one practical question: do they pull together, or does one hold the other back? We ran this exact combination across all supported resolutions to answer it with numbers rather than guesswork.
Straight answer: aim for 1080p
At 1080p the Ryzen 5 3600 becomes the limiting part (~19% CPU bottleneck), whereas at 4K the RX 6800 is the limiting part (~42% GPU bottleneck). We put the target at 1080p: the highest of the usual 16:9 sizes where AAA titles still return 74 FPS, which is above 60. The table below breaks out all twelve resolutions on their own, ultrawide formats included.
Think of resolution as a dial that splits the weight between CPU and GPU. Drop to 1080p and you wring out the RX 6800 while leaning harder on the Ryzen 5 3600; push to 4K and the opposite happens. Synergy here swings between 58% and 81% depending on where you sit.
Down to real numbers: In esports titles like Valorant this pair flies — around 341 FPS at 1080p, plenty for a high-refresh monitor. At the other end, a demanding AAA like Alan Wake 2 drops to ~18 FPS at 4K, which is where the RX 6800's ceiling really shows. Overall, expect about 74 FPS average in AAA games at 1080p and around 34 FPS at 4K.
[CPU] Ryzen 5 3600
The Ryzen 5 3600 scores 52/100 on this model's gaming scale, with 6 cores and 12 threads. With 32 MB of L3 cache it has room to keep the RX 6800 well fed. In this pairing its job is to serve frames fast enough to never leave the graphics card waiting.
[GPU] RX 6800
The RX 6800 (34/100 on the model's gaming scale) supplies the raster muscle of the build. Its 16 GB of GDDR6 set how far it can go on resolution and texture quality before video memory runs short.
A detail that's easy to overlook: Both parts come from nearby generations, which usually means a natural pairing with no platform surprises. You're combining an AMD platform with an AMD GPU — a perfectly valid mix that imposes no penalty.
DO YOU NEED TO CHANGE ANYTHING?
At 1440p neither part appreciably holds the other back, so there is nothing you need to change. The Ryzen 5 3600 and the RX 6800 stand as they are; a 650W supply gives the build headroom.
PRICE OF EACH PART
Affiliate links — we earn a small commission at no cost to you. Full disclosure
SPECIFICATIONS
CATALOGUE DATA[CPU] AMD Ryzen 5 3600
- Cores6C / 12T
- Clock3.6 – 4.2 GHz
- TDP65 W
- SocketAM4
- Single-thread2,581
- Multi-thread17,855
- L3 cache32 MB
[GPU] AMD RX 6800
- VRAM16 GB GDDR6
- Memory bus256-bit
- TDP250 W
- G3D Mark22,070
- Memory bandwidth512 GB/s
BOTTLENECK BY RESOLUTION
SYNERGY · AVERAGE FPSYour CPU (Ryzen 5 3600) partially limits the RX 6800 at 1920x1080. In CPU-heavy scenes you will lose frames. Consider a CPU upgrade or a higher target resolution.
Your CPU (Ryzen 5 3600) and GPU (RX 6800) are an exceptionally balanced match for gaming at 2560x1440. No realistic component swap would meaningfully improve this build.
Your GPU (RX 6800) is the limiting factor at 3440x1440 (Ultrawide 21:9). In graphically demanding titles you will see lower frame rates; a faster GPU would deliver a clear improvement.
Your GPU (RX 6800) severely limits the system at 5120x1440 (Super Ultrawide 32:9), leaving the Ryzen 5 3600 heavily underused. A faster GPU would improve performance dramatically.
Your GPU (RX 6800) severely limits the system at 4K, leaving the Ryzen 5 3600 heavily underused. A faster GPU would improve performance dramatically.
ESTIMATED FPS BY GAME
1920x1080SYSTEM DIAGNOSTICS
POWER · VRAM & PCIe · RAMPOWER ESTIMATION
The Ryzen 5 3600 (65W) and RX 6800 (250W) add up to roughly 315W under load. Adding 150W for the rest of the system gives 465W, and with a 30% transient margin, 650W is the safe figure.
VIDEO MEMORY AND PCIe
The RX 6800's memory bus (256-bit) and bandwidth (512 GB/s) describe its own video memory, meaning how fast the card reads its 16 GB of GDDR6, not the PCIe link to the processor. The PCIe link depends on the card, the processor and the motherboard slot together; our catalogue does not record PCIe generation or lane count, so the model does not estimate it. It matters most for cards with an eight-lane interface in older PCIe 3.0 boards: check the card's and the board's specifications.
SYSTEM MEMORY
This page assumes 16 GB in dual channel. At 1080p, the resolution recommended above, that meets the model's capacity target of 16 GB (enough for three in four of the games it covers), so more capacity would add little or nothing there. The target stays at 16 GB even at 4K, so a larger kit is for heavy multitasking or mods, not for these games. Memory speed and a second channel act on the processor's ceiling instead: they matter in the games the CPU limits, by an amount that depends on the game, and the calculator lets you enter your own kit.
HOW THIS PAGE IS CALCULATED
ENGINE v2026.08 · 2026-09-11CALCULATED, NOT WRITTEN
Every figure and every sentence comes from the same deterministic engine, driven by the catalogue specifications. That is what makes it reproducible: with the same engine version (2026.08) and the same catalogue, the same pairing always gives the same result. When either changes, the version and date above change with it, and the changelog says why.
WHERE THE DATA COMES FROM
Specifications come from the official AMD, Intel and NVIDIA datasheets together with PassMark and TechPowerUp. The gaming indices are calibrated against frame rates published by review outlets (TechPowerUp, TechSpot / Hardware Unboxed, Tom's Hardware, Gamers Nexus, Digital Foundry) rather than synthetic scores. That data is compiled, not measured here: this site runs no test bench of its own.
STATED LIMITS
Figures estimate native raster performance at high/ultra quality, with no ray tracing, upscaling or frame generation. We do not yet publish an externally validated error margin — the accuracy page states exactly where that stands.
* Affiliate disclosure: the Amazon links exist to show pricing. As an Amazon Associate we earn from qualifying purchases at no extra cost to you. Recommendation order is decided by the engine and does not depend on commission.
TRY WITH YOUR OWN HARDWARE
Customize RAM, resolution, and discover upgrade recommendations.
FREQUENTLY ASKED QUESTIONS
5Does the AMD Ryzen 5 3600 bottleneck the AMD RX 6800?
At 1080p the Ryzen 5 3600 becomes the limiting part (~19% CPU bottleneck), whereas at 4K the RX 6800 is the limiting part (~42% GPU bottleneck). Overall, the GPU is the limit at high resolution, with 67% average efficiency across the 12 resolutions our model tests. The resolution we would target with this pair is 1080p, where AAA games average 74 FPS.
How many FPS do the Ryzen 5 3600 and RX 6800 get at 1080p?
At 1080p this combination averages about 74 FPS in AAA games and around 220 FPS in esports titles. In Valorant we estimate up to 341 FPS.
Is this pairing good for 4K gaming?
Playable rather than smooth: about 34 FPS on average in AAA titles at 4K, with the RX 6800 setting the limit. Upscaling (DLSS, FSR or XeSS) or lower settings are the usual way to reach 60 FPS.
What power supply do I need for the Ryzen 5 3600 and RX 6800?
With an estimated combined draw of 315W across CPU and GPU, we recommend at least a 650W 80+ Gold supply (ideally ATX 3.0) to run with headroom.
Is the RX 6800's 16 GB of VRAM enough?
In the model, 16 GB covers all 11 games it tracks even at 4K with high textures, so video memory is not the constraint for this pairing.