| | | | | | |

Core m3-7Y30 vs Mobile 3020e


Description
The m3-7Y30 is based on Kaby Lake architecture while the 3020e is based on Zen.

Using the multithread performance as a reference, the m3-7Y30 gets a score of 52.8 k points while the 3020e gets 52.4 k points.

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

Specs
CPUID
806e9
820f01
Core
Kaby Lake
Dali
Architecture
Base frecuency
1 GHz
1.2 GHz
Boost frecuency
2.6 GHz
2.6 GHz
Socket
BGA 1515
BGA 1140
Cores/Threads
2/4
2/2
TDP
4.5 W
6 W
Cache L1 (d+i)
2x32+2x32 kB
2x64+2x32 kB
Cache L2
2x256 kB
2x512 kB
Cache L3
4096 kB
4096 kB
Date
August 2016
January 2020
Mean monothread perf.
25.6k points
29.34k points
Mean multithread perf.
52.78k points
52.42k 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
3020e
Test#1 (Integers)
10.02k
9.28k (x0.93)
Test#2 (FP)
9.22k
14.56k (x1.58)
Test#3 (Generic, ZIP)
2.04k
3.44k (x1.68)
Test#1 (Memory)
4.31k
2.06k (x0.48)
TOTAL
25.6k
29.34k (x1.15)

Multithread

m3-7Y30

3020e
Test#1 (Integers)
21.75k
15.75k (x0.72)
Test#2 (FP)
20.51k
28.63k (x1.4)
Test#3 (Generic, ZIP)
4.97k
5.87k (x1.18)
Test#1 (Memory)
5.56k
2.17k (x0.39)
TOTAL
52.78k
52.42k (x0.99)

Performance/W
m3-7Y30
3020e
Test#1 (Integers)
4832 points/W
2625 points/W
Test#2 (FP)
4557 points/W
4771 points/W
Test#3 (Generic, ZIP)
1104 points/W
979 points/W
Test#1 (Memory)
1236 points/W
361 points/W
TOTAL
11730 points/W
8737 points/W

Performance/GHz
m3-7Y30
3020e
Test#1 (Integers)
3852 points/GHz
3570 points/GHz
Test#2 (FP)
3547 points/GHz
5602 points/GHz
Test#3 (Generic, ZIP)
786 points/GHz
1323 points/GHz
Test#1 (Memory)
1659 points/GHz
792 points/GHz
TOTAL
9844 points/GHz
11287 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