| | | | | | |

Core i3-7100U vs Mobile 3020e


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

Using the multithread performance as a reference, the i3-7100U gets a score of 79.6 k points while the 3020e gets 52.4 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
806e9
820f01
Core
Kaby Lake-U
Dali
Architecture
Base frecuency
2.4 GHz
1.2 GHz
Boost frecuency
2.4 GHz
2.6 GHz
Socket
BGA 1356
BGA 1140
Cores/Threads
2/4
2/2
TDP
15 W
6 W
Cache L1 (d+i)
2x32+2x32 kB
2x64+2x32 kB
Cache L2
2x256 kB
2x512 kB
Cache L3
3072 kB
4096 kB
Date
August 2016
January 2020
Mean monothread perf.
33.38k points
29.34k points
Mean multithread perf.
79.6k 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
i3-7100U
3020e
Test#1 (Integers)
13.46k
9.28k (x0.69)
Test#2 (FP)
13.45k
14.56k (x1.08)
Test#3 (Generic, ZIP)
3.08k
3.44k (x1.12)
Test#1 (Memory)
3.4k
2.06k (x0.61)
TOTAL
33.38k
29.34k (x0.88)

Multithread

i3-7100U

3020e
Test#1 (Integers)
34.95k
15.75k (x0.45)
Test#2 (FP)
33.53k
28.63k (x0.85)
Test#3 (Generic, ZIP)
7.74k
5.87k (x0.76)
Test#1 (Memory)
3.38k
2.17k (x0.64)
TOTAL
79.6k
52.42k (x0.66)

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

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