| | | | | | |

Ryzen 5 3500U vs Core m3-7Y30


Description
The 3500U is based on Zen+ architecture while the m3-7Y30 is based on Kaby Lake.

Using the multithread performance as a reference, the 3500U gets a score of 141 k points while the m3-7Y30 gets 52.8 k points.

Summarizing, the 3500U is 2.7 times faster than the m3-7Y30. To get a proper comparison between both models, take a look to the data shown below.

Specs
CPUID
810f81
806e9
Core
Picasso
Kaby Lake
Architecture
Base frecuency
2.1 GHz
1 GHz
Boost frecuency
3.7 GHz
2.6 GHz
Socket
BGA-FP5
BGA 1515
Cores/Threads
4/8
2/4
TDP
15 W
4.5 W
Cache L1 (d+i)
4x64+6x32 kB
2x32+2x32 kB
Cache L2
4x512 kB
2x256 kB
Cache L3
4096 kB
4096 kB
Date
January 2019
August 2016
Mean monothread perf.
36.64k points
25.6k points
Mean multithread perf.
140.97k points
52.78k points

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
3500U
m3-7Y30
Test#1 (Integers)
10.88k
10.02k (x0.92)
Test#2 (FP)
18.09k
9.22k (x0.51)
Test#3 (Generic, ZIP)
4.29k
2.04k (x0.48)
Test#1 (Memory)
3.36k
4.31k (x1.28)
TOTAL
36.64k
25.6k (x0.7)

Multithread

3500U

m3-7Y30
Test#1 (Integers)
42.44k
21.75k (x0.51)
Test#2 (FP)
73.82k
20.51k (x0.28)
Test#3 (Generic, ZIP)
20.76k
4.97k (x0.24)
Test#1 (Memory)
3.96k
5.56k (x1.41)
TOTAL
140.97k
52.78k (x0.37)

Performance/W
3500U
m3-7Y30
Test#1 (Integers)
2829 points/W
4832 points/W
Test#2 (FP)
4921 points/W
4557 points/W
Test#3 (Generic, ZIP)
1384 points/W
1104 points/W
Test#1 (Memory)
264 points/W
1236 points/W
TOTAL
9398 points/W
11730 points/W

Performance/GHz
3500U
m3-7Y30
Test#1 (Integers)
2942 points/GHz
3852 points/GHz
Test#2 (FP)
4890 points/GHz
3547 points/GHz
Test#3 (Generic, ZIP)
1161 points/GHz
786 points/GHz
Test#1 (Memory)
909 points/GHz
1659 points/GHz
TOTAL
9901 points/GHz
9844 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