| | | | | | |

Ryzen 7 2700X vs Core i5-5200U


Description
The 2700X is based on Zen+ architecture while the i5-5200U is based on Broadwell.

Using the multithread performance as a reference, the 2700X gets a score of 431.1 k points while the i5-5200U gets 68.7 k points.

Summarizing, the 2700X is 6.3 times faster than the i5-5200U . To get a proper comparison between both models, take a look to the data shown below.

Specs
CPUID
800f82
306d4
Core
Pinnacle Ridge
Broadwell-U
Architecture
Base frecuency
3.7 GHz
2.2 GHz
Boost frecuency
4.3 GHz
2.7 GHz
Socket
AM4
Cores/Threads
8/16
2 /4
TDP
105 W
15 W
Cache L1 (d+i)
8x64+8x32 kB
2x32+2x32 kB
Cache L2
8x512 kB
256 kB
Cache L3
16384 kB
3072 kB
Date
April 2018
March 2015
Mean monothread perf.
64.83k points
31.81k points
Mean multithread perf.
431.14k points
68.69k points

Non-optimized benchmark
The benchmark in Mode 0 (FPU) measures cpu performance with non-optimized software. It uses the basic µinstructions from the i386 architecture with the i387 floating point unit. This mode is compatible with all CPUs so it's practical to compare very different CPUs
Monothread
2700X
i5-5200U
Test#1 (Integers)
4.25k
2.67k (x0.63)
Test#2 (FP)
19.72k
9.37k (x0.48)
Test#3 (Generic, ZIP)
5.84k
3.13k (x0.54)
Test#1 (Memory)
21.36k
2.59k (x0.12)
TOTAL
51.17k
17.76k (x0.35)

Multithread

2700X

i5-5200U
Test#1 (Integers)
35.04k
4.16k (x0.12)
Test#2 (FP)
181.42k
19.01k (x0.1)
Test#3 (Generic, ZIP)
64.86k
6.48k (x0.1)
Test#1 (Memory)
8.21k
2.96k (x0.36)
TOTAL
289.54k
32.61k (x0.11)

AVX optimized benchmark
The benchmark in mode II (AVX) is optimized to used 256 bits registers beside the first version of the Advanced Vector Extensions (AVX). The first AVX compatible CPU was released in 2011.
Monothread
2700X
i5-5200U
Test#1 (Integers)
14.44k
8.48k (x0.59)
Test#2 (FP)
24.92k
12.03k (x0.48)
Test#3 (Generic, ZIP)
5.8k
3.32k (x0.57)
Test#1 (Memory)
19.07k
2.79k (x0.15)
TOTAL
64.24k
26.62k (x0.41)

Multithread

2700X

i5-5200U
Test#1 (Integers)
122.01k
15.19k (x0.12)
Test#2 (FP)
220.34k
25.99k (x0.12)
Test#3 (Generic, ZIP)
59.89k
6.71k (x0.11)
Test#1 (Memory)
9.9k
2.96k (x0.3)
TOTAL
412.13k
50.85k (x0.12)

AVX2 optimized benchmark
The benchmark in mode III (AVX2), like AVX1, is optimized to used 256 bits registers beside the second version of the Advanced Vector Extensions (AVX). The first AVX2 compatible CPU was released in 2013.
Monothread
2700X
i5-5200U
Test#1 (Integers)
15.34k
13.58k (x0.89)
Test#2 (FP)
25.75k
12.14k (x0.47)
Test#3 (Generic, ZIP)
5.79k
3.18k (x0.55)
Test#1 (Memory)
17.95k
2.92k (x0.16)
TOTAL
64.83k
31.81k (x0.49)

Multithread

2700X

i5-5200U
Test#1 (Integers)
123.07k
28.89k (x0.23)
Test#2 (FP)
239.3k
28.74k (x0.12)
Test#3 (Generic, ZIP)
60.6k
7.31k (x0.12)
Test#1 (Memory)
8.18k
3.74k (x0.46)
TOTAL
431.14k
68.69k (x0.16)

Performance/W
2700X
i5-5200U
Test#1 (Integers)
1172 points/W
1926 points/W
Test#2 (FP)
2279 points/W
1916 points/W
Test#3 (Generic, ZIP)
577 points/W
488 points/W
Test#1 (Memory)
78 points/W
249 points/W
TOTAL
4106 points/W
4579 points/W

Performance/GHz
2700X
i5-5200U
Test#1 (Integers)
3568 points/GHz
5029 points/GHz
Test#2 (FP)
5987 points/GHz
4497 points/GHz
Test#3 (Generic, ZIP)
1347 points/GHz
1176 points/GHz
Test#1 (Memory)
4175 points/GHz
1080 points/GHz
TOTAL
15078 points/GHz
11782 points/GHz

Monothread performance graph
Monothread performance graphics gives the performance vs time. They are useful to measure the time it takes to the CPU to reach the maximum performance.

Usually, CPU's performance will be steady during these tests but if it has a slow frequency strategy, the first samples will show a lower score.


Test#1 (Integers) [points vs time]

grafica bm.hardlimit.com


Test#2 (FP) [points vs time]

grafica bm.hardlimit.com


Test#3 (Generic, ZIP) [points vs time]

grafica bm.hardlimit.com


Test#1 (Memory) [points vs time]

grafica bm.hardlimit.com

Multithread performance graph
Multithread graphs measure the performance against a heavy load during certain time.

If CPU's TDP doesn't limit the frequency and the machine is properly cooled, performance should remain steady vs time. Otherwise, the performance score will oscillate or decrease over time.


Test#1 (Integers) [points vs time]

grafica bm.hardlimit.com


Test#2 (FP) [points vs time]

grafica bm.hardlimit.com


Test#3 (Generic, ZIP) [points vs time]

grafica bm.hardlimit.com


Test#1 (Memory) [points vs time]

grafica bm.hardlimit.com

Hardlimit Benchmark Central - Ver. 3.11.4