| | | | | | |

Core m3-7Y30 vs Ryzen 5 3500U


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

Using the multithread performance as a reference, the m3-7Y30 gets a score of 52.8 k points while the 3500U gets 141 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
806e9
810f81
Core
Kaby Lake
Picasso
Architecture
Base frecuency
1 GHz
2.1 GHz
Boost frecuency
2.6 GHz
3.7 GHz
Socket
BGA 1515
BGA-FP5
Cores/Threads
2/4
4/8
TDP
4.5 W
15 W
Cache L1 (d+i)
2x32+2x32 kB
4x64+6x32 kB
Cache L2
2x256 kB
4x512 kB
Cache L3
4096 kB
4096 kB
Date
August 2016
January 2019
Mean monothread perf.
25.6k points
36.64k points
Mean multithread perf.
52.78k points
140.97k 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
m3-7Y30
3500U
Test#1 (Integers)
10.02k
10.88k (x1.09)
Test#2 (FP)
9.22k
18.09k (x1.96)
Test#3 (Generic, ZIP)
2.04k
4.29k (x2.1)
Test#1 (Memory)
4.31k
3.36k (x0.78)
TOTAL
25.6k
36.64k (x1.43)

Multithread

m3-7Y30

3500U
Test#1 (Integers)
21.75k
42.44k (x1.95)
Test#2 (FP)
20.51k
73.82k (x3.6)
Test#3 (Generic, ZIP)
4.97k
20.76k (x4.18)
Test#1 (Memory)
5.56k
3.96k (x0.71)
TOTAL
52.78k
140.97k (x2.67)

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

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