| | | | | | |

Core i5-5200U vs i3-7100U


Description
The i5-5200U is based on Broadwell architecture while the i3-7100U is based on Kaby Lake.

Using the multithread performance as a reference, the i5-5200U gets a score of 68.7 k points while the i3-7100U gets 79.6 k points.

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

Specs
CPUID
306d4
806e9
Core
Broadwell-U
Kaby Lake-U
Architecture
Base frecuency
2.2 GHz
2.4 GHz
Boost frecuency
2.7 GHz
2.4 GHz
Socket
BGA 1356
Cores/Threads
2 /4
2/4
TDP
15 W
15 W
Cache L1 (d+i)
2x32+2x32 kB
2x32+2x32 kB
Cache L2
256 kB
2x256 kB
Cache L3
3072 kB
3072 kB
Date
March 2015
August 2016
Mean monothread perf.
31.81k points
33.38k points
Mean multithread perf.
68.69k points
79.6k points

Non-optimized benchmark
The benchmark in Mode 0 (FPU) measures cpu performance with non-optimized software. It uses the basic µinstructions from the i386 architecture with the i387 floating point unit. This mode is compatible with all CPUs so it's practical to compare very different CPUs
Monothread
i5-5200U
i3-7100U
Test#1 (Integers)
2.67k
2.41k (x0.9)
Test#2 (FP)
9.37k
9.77k (x1.04)
Test#3 (Generic, ZIP)
3.13k
3.13k (x1)
Test#1 (Memory)
2.59k
3.55k (x1.37)
TOTAL
17.76k
18.86k (x1.06)

Multithread

i5-5200U

i3-7100U
Test#1 (Integers)
4.16k
5k (x1.2)
Test#2 (FP)
19.01k
21.48k (x1.13)
Test#3 (Generic, ZIP)
6.48k
7.39k (x1.14)
Test#1 (Memory)
2.96k
3.18k (x1.07)
TOTAL
32.61k
37.05k (x1.14)

AVX optimized benchmark
The benchmark in mode II (AVX) is optimized to used 256 bits registers beside the first version of the Advanced Vector Extensions (AVX). The first AVX compatible CPU was released in 2011.
Monothread
i5-5200U
i3-7100U
Test#1 (Integers)
8.48k
8.76k (x1.03)
Test#2 (FP)
12.03k
13.49k (x1.12)
Test#3 (Generic, ZIP)
3.32k
3.21k (x0.97)
Test#1 (Memory)
2.79k
3.9k (x1.4)
TOTAL
26.62k
29.36k (x1.1)

Multithread

i5-5200U

i3-7100U
Test#1 (Integers)
15.19k
18.33k (x1.21)
Test#2 (FP)
25.99k
31.08k (x1.2)
Test#3 (Generic, ZIP)
6.71k
7.5k (x1.12)
Test#1 (Memory)
2.96k
3.61k (x1.22)
TOTAL
50.85k
60.52k (x1.19)

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
i5-5200U
i3-7100U
Test#1 (Integers)
13.58k
13.46k (x0.99)
Test#2 (FP)
12.14k
13.45k (x1.11)
Test#3 (Generic, ZIP)
3.18k
3.08k (x0.97)
Test#1 (Memory)
2.92k
3.4k (x1.16)
TOTAL
31.81k
33.38k (x1.05)

Multithread

i5-5200U

i3-7100U
Test#1 (Integers)
28.89k
34.95k (x1.21)
Test#2 (FP)
28.74k
33.53k (x1.17)
Test#3 (Generic, ZIP)
7.31k
7.74k (x1.06)
Test#1 (Memory)
3.74k
3.38k (x0.9)
TOTAL
68.69k
79.6k (x1.16)

Performance/W
i5-5200U
i3-7100U
Test#1 (Integers)
1926 points/W
2330 points/W
Test#2 (FP)
1916 points/W
2235 points/W
Test#3 (Generic, ZIP)
488 points/W
516 points/W
Test#1 (Memory)
249 points/W
225 points/W
TOTAL
4579 points/W
5307 points/W

Performance/GHz
i5-5200U
i3-7100U
Test#1 (Integers)
5029 points/GHz
5606 points/GHz
Test#2 (FP)
4497 points/GHz
5606 points/GHz
Test#3 (Generic, ZIP)
1176 points/GHz
1282 points/GHz
Test#1 (Memory)
1080 points/GHz
1415 points/GHz
TOTAL
11782 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