AMD Ryzen 5 5600X vs Intel Core i5-7200U vs Intel Core i7-7Y75

AMD Ryzen 5 5600X

The AMD Ryzen 5 5600X is a desktop processor with 6 SMT-enabled (12 threads) and based on the Zen 3 architecture. Launched in November 2020, it is the fastest 6-core Ryzen desktop processor. With a TDP of 65 watts, the Ryzen 5 5600X is the least energy-hungry model in the Zen 3 family to date.

The Ryzen 5 5600X is clocked at 3.7 GHz base clock and can be clocked up to 4.6 GHz with Precision Boost 2.

Performance

The average 5600X in our database is in the same league as the Ryzen 9 4900H and the Ryzen 7 6800HS, as far as multi-thread benchmark scores are concerned. While this isn't the fastest CPU money can buy, it still rips through most workloads with ease, as of mid 2022. Find out more in our full review.

Power consumption

This Ryzen 5 series chip has a default TDP (also known as the long-term power limit) of 65 W to be in line with most desktop processors.

The R5 5600X is built with TSMC's 7 nm process for average, as of early 2023, energy efficiency.

Intel Core i5-7200U

The Intel Core i5-7200U is a dual-core processor of the Kaby Lake architecture. It offers two CPU cores clocked at 2.5 - 3.1 GHz and integrates HyperThreading to work with up to 4 threads at once. The architectural differences are rather small compared to the Skylake generation, therefore the performance per MHz is very similar. The SoC includes a dual channel DDR4 memory controller and Intel HD Graphics 620 graphics card (clocked at 300 - 1000 MHz). It is manufactured in an improved 14nm FinFET process at Intel. Compared to the old Skylake based Core i5-6200U, the i5-7200U offers a 300 MHz higher clock speed.

Intel Core i7-7Y75

The Intel Core i7-7Y75 is a very efficient dual-core SoC for tablets and passively cooled notebooks based on the Kaby Lake architecture and was announced in the end of August 2016. The CPU consists of two processor cores clocked at 1.3-3.6 GHz (2-core Turbo not specified yet). Thanks to Hyper Threading, the processor can execute up to four threads simultaneously. The chips also includes the Intel HD Graphics 615 GPU, a dual-channel memory controller (DDR3L/LPDDR3) as well as VP9 and H.265 video de- and encoder. It is still produced in a 14 nm process with FinFET transistors. 

Architecture

Intel basically used the familiar micro architecture from the Skylake generation, so the per-MHz performance is identical. Only the Speed-Shift technology for faster dynamic adjustments of the voltages and clocks was improved, and the matured 14 nm process now also enables much higher frequencies and better efficiency than before. 

Performance

Despite the changed designation, the Core i7-7Y75 is the successor to the Core m7-6Y75 (Skylake Y-series), so the chip does not reach the performance level of other Core i processors due to the lower TDP. Thanks to its high Turbo clock, the 7Y75 can sometimes keep up with the 15 Watt models for short peak load and single-thread scenarios, but the clocks will drop significantly under sustained workloads. The CPU is still suitable for many more demanding applications as well as multitasking. 

Graphics

The integrated Intel HD Graphics 615 GPU has 24 Execution Units (EUs) like the old HD Graphics 515 and runs with clocks between 300 and 1050 MHz in combination with this processor. The performance heavily depends on the TDP limit as well as the memory configuration; with fast LPDDR3-1866 RAM in dual-channel mode, the GPU should sometimes be able to compete with the HD Graphics 520, but can also be much slower in other scenarios. Modern games from 2016 will, if at all, only run smoothly in the lowest settings.

Contrary to Skylake, Kaby Lake now also supports hardware decoding for H.265/HEVC Main10 with a 10-bit color depth as well as Google's VP9 codec.

Power Consumption

The chip is manufactured in an improved 14 nm process with FinFET transistors, so the power efficiency was once again improved significantly. The typical TDP for the Y-series is specified at 4.5 Watts, and can be adjusted in both directions depending on the usage scenario.