| | | | | | |

Mobile 3020e vs Core i3-7100U


Description
The 3020e is based on Zen architecture while the i3-7100U is based on Kaby Lake.

Using the multithread performance as a reference, the 3020e gets a score of 52.4 k points while the i3-7100U gets 79.6 k points.

Summarizing, the i3-7100U is 1.5 times faster than the 3020e. To get a proper comparison between both models, take a look to the data shown below.

Specs
CPUID
820f01
806e9
Core
Dali
Kaby Lake-U
Architecture
Base frecuency
1.2 GHz
2.4 GHz
Boost frecuency
2.6 GHz
2.4 GHz
Socket
BGA 1140
BGA 1356
Cores/Threads
2/2
2/4
TDP
6 W
15 W
Cache L1 (d+i)
2x64+2x32 kB
2x32+2x32 kB
Cache L2
2x512 kB
2x256 kB
Cache L3
4096 kB
3072 kB
Date
January 2020
August 2016
Mean monothread perf.
29.34k points
33.38k points
Mean multithread perf.
52.42k points
79.6k 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
3020e
i3-7100U
Test#1 (Integers)
9.28k
13.46k (x1.45)
Test#2 (FP)
14.56k
13.45k (x0.92)
Test#3 (Generic, ZIP)
3.44k
3.08k (x0.89)
Test#1 (Memory)
2.06k
3.4k (x1.65)
TOTAL
29.34k
33.38k (x1.14)

Multithread

3020e

i3-7100U
Test#1 (Integers)
15.75k
34.95k (x2.22)
Test#2 (FP)
28.63k
33.53k (x1.17)
Test#3 (Generic, ZIP)
5.87k
7.74k (x1.32)
Test#1 (Memory)
2.17k
3.38k (x1.56)
TOTAL
52.42k
79.6k (x1.52)

Performance/W
3020e
i3-7100U
Test#1 (Integers)
2625 points/W
2330 points/W
Test#2 (FP)
4771 points/W
2235 points/W
Test#3 (Generic, ZIP)
979 points/W
516 points/W
Test#1 (Memory)
361 points/W
225 points/W
TOTAL
8737 points/W
5307 points/W

Performance/GHz
3020e
i3-7100U
Test#1 (Integers)
3570 points/GHz
5606 points/GHz
Test#2 (FP)
5602 points/GHz
5606 points/GHz
Test#3 (Generic, ZIP)
1323 points/GHz
1282 points/GHz
Test#1 (Memory)
792 points/GHz
1415 points/GHz
TOTAL
11287 points/GHz
13909 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