| | | | | | |

Core m3-7Y30 vs Ryzen 5 3550H


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

Using the multithread performance as a reference, the m3-7Y30 gets a score of 52.8 k points while the 3550H gets 178.3 k points.

Summarizing, the 3550H is 3.4 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
35 W
Cache L1 (d+i)
2x32+2x32 kB
4x64+4x32 kB
Cache L2
2x256 kB
4x512 kB
Cache L3
4096 kB
4096 kB
Date
August 2016
January 2019
Mean monothread perf.
25.6k points
45.07k points
Mean multithread perf.
52.78k points
178.26k 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
3550H
Test#1 (Integers)
10.02k
13.51k (x1.35)
Test#2 (FP)
9.22k
22.34k (x2.42)
Test#3 (Generic, ZIP)
2.04k
4.98k (x2.44)
Test#1 (Memory)
4.31k
4.24k (x0.98)
TOTAL
25.6k
45.07k (x1.76)

Multithread

m3-7Y30

3550H
Test#1 (Integers)
21.75k
52.21k (x2.4)
Test#2 (FP)
20.51k
95.66k (x4.66)
Test#3 (Generic, ZIP)
4.97k
25.54k (x5.14)
Test#1 (Memory)
5.56k
4.85k (x0.87)
TOTAL
52.78k
178.26k (x3.38)

Performance/W
m3-7Y30
3550H
Test#1 (Integers)
4832 points/W
1492 points/W
Test#2 (FP)
4557 points/W
2733 points/W
Test#3 (Generic, ZIP)
1104 points/W
730 points/W
Test#1 (Memory)
1236 points/W
139 points/W
TOTAL
11730 points/W
5093 points/W

Performance/GHz
m3-7Y30
3550H
Test#1 (Integers)
3852 points/GHz
3652 points/GHz
Test#2 (FP)
3547 points/GHz
6038 points/GHz
Test#3 (Generic, ZIP)
786 points/GHz
1347 points/GHz
Test#1 (Memory)
1659 points/GHz
1145 points/GHz
TOTAL
9844 points/GHz
12182 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