| | | | | | |

Core i5-5200U vs i3-6100


Description
The i5-5200U is based on Broadwell architecture while the i3-6100 is based on Skylake.

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

Summarizing, the i3-6100 is 1.6 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
506e3
Core
Broadwell-U
Skylake-S
Architecture
Base frecuency
2.2 GHz
3.7 GHz
Boost frecuency
2.7 GHz
3.7 GHz
Socket
LGA 1151
Cores/Threads
2 /4
2/2
TDP
15 W
51 W
Cache L1 (d+i)
2x32+2x32 kB
32+32 kB
Cache L2
256 kB
256 kB
Cache L3
3072 kB
4096 kB
Date
March 2015
September 2015
Mean monothread perf.
31.81k points
52.84k points
Mean multithread perf.
68.69k points
112.28k 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-6100
Test#1 (Integers)
2.67k
3.81k (x1.43)
Test#2 (FP)
9.37k
15.65k (x1.67)
Test#3 (Generic, ZIP)
3.13k
5.14k (x1.64)
Test#1 (Memory)
2.59k
4.28k (x1.65)
TOTAL
17.76k
28.89k (x1.63)

Multithread

i5-5200U

i3-6100
Test#1 (Integers)
4.16k
7.75k (x1.86)
Test#2 (FP)
19.01k
37.33k (x1.96)
Test#3 (Generic, ZIP)
6.48k
12.13k (x1.87)
Test#1 (Memory)
2.96k
3.56k (x1.2)
TOTAL
32.61k
60.77k (x1.86)

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-6100
Test#1 (Integers)
8.48k
13.78k (x1.62)
Test#2 (FP)
12.03k
21.21k (x1.76)
Test#3 (Generic, ZIP)
3.32k
5.2k (x1.57)
Test#1 (Memory)
2.79k
3.73k (x1.34)
TOTAL
26.62k
43.92k (x1.65)

Multithread

i5-5200U

i3-6100
Test#1 (Integers)
15.19k
29.02k (x1.91)
Test#2 (FP)
25.99k
49.55k (x1.91)
Test#3 (Generic, ZIP)
6.71k
12.3k (x1.83)
Test#1 (Memory)
2.96k
3.28k (x1.11)
TOTAL
50.85k
94.15k (x1.85)

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-6100
Test#1 (Integers)
13.58k
22.89k (x1.69)
Test#2 (FP)
12.14k
21.04k (x1.73)
Test#3 (Generic, ZIP)
3.18k
4.9k (x1.54)
Test#1 (Memory)
2.92k
4.01k (x1.37)
TOTAL
31.81k
52.84k (x1.66)

Multithread

i5-5200U

i3-6100
Test#1 (Integers)
28.89k
50.05k (x1.73)
Test#2 (FP)
28.74k
47.13k (x1.64)
Test#3 (Generic, ZIP)
7.31k
11.38k (x1.56)
Test#1 (Memory)
3.74k
3.72k (x0.99)
TOTAL
68.69k
112.28k (x1.63)

Performance/W
i5-5200U
i3-6100
Test#1 (Integers)
1926 points/W
981 points/W
Test#2 (FP)
1916 points/W
924 points/W
Test#3 (Generic, ZIP)
488 points/W
223 points/W
Test#1 (Memory)
249 points/W
73 points/W
TOTAL
4579 points/W
2202 points/W

Performance/GHz
i5-5200U
i3-6100
Test#1 (Integers)
5029 points/GHz
6187 points/GHz
Test#2 (FP)
4497 points/GHz
5686 points/GHz
Test#3 (Generic, ZIP)
1176 points/GHz
1325 points/GHz
Test#1 (Memory)
1080 points/GHz
1084 points/GHz
TOTAL
11782 points/GHz
14282 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