| | | | | | |

Core i3-7100 vs i5-6500


Description
The i3-7100 is based on Kaby Lake architecture while the i5-6500 is based on Skylake.

Using the multithread performance as a reference, the i3-7100 gets a score of 124.8 k points while the i5-6500 gets 179.4 k points.

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

Specs
CPUID
906e9
506e3
Core
Kaby Lake-S
Skylake-S
Architecture
Base frecuency
3.9 GHz
3.2 GHz
Boost frecuency
3.9 GHz
3.6 GHz
Socket
LGA 1151
LGA 1151
Cores/Threads
2/4
4/4
TDP
51 W
65 W
Cache L1 (d+i)
2x32+2x32 kB
4x32+4x32 kB
Cache L2
2x256 kB
4x256 kB
Cache L3
3072 kB
6144 kB
Date
January 2017
September 2015
Mean monothread perf.
57.86k points
53.7k points
Mean multithread perf.
124.8k points
179.44k 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
i3-7100
i5-6500
Test#1 (Integers)
4.01k
3.46k (x0.86)
Test#2 (FP)
16.38k
14.61k (x0.89)
Test#3 (Generic, ZIP)
5.31k
4.66k (x0.88)
Test#1 (Memory)
3.98k
6.99k (x1.75)
TOTAL
29.69k
29.71k (x1)

Multithread

i3-7100

i5-6500
Test#1 (Integers)
8.1k
12.52k (x1.55)
Test#2 (FP)
38.7k
51.13k (x1.32)
Test#3 (Generic, ZIP)
12.69k
17.41k (x1.37)
Test#1 (Memory)
3.76k
3.9k (x1.04)
TOTAL
63.24k
84.96k (x1.34)

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
i3-7100
i5-6500
Test#1 (Integers)
14.41k
13.07k (x0.91)
Test#2 (FP)
22.38k
20.23k (x0.9)
Test#3 (Generic, ZIP)
5.45k
4.93k (x0.9)
Test#1 (Memory)
4.96k
9.2k (x1.85)
TOTAL
47.21k
47.43k (x1)

Multithread

i3-7100

i5-6500
Test#1 (Integers)
30.48k
49.62k (x1.63)
Test#2 (FP)
52.08k
74.82k (x1.44)
Test#3 (Generic, ZIP)
12.97k
18.46k (x1.42)
Test#1 (Memory)
4.56k
4.21k (x0.92)
TOTAL
100.1k
147.12k (x1.47)

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-7100
i5-6500
Test#1 (Integers)
25.53k
22.89k (x0.9)
Test#2 (FP)
22.98k
19.87k (x0.86)
Test#3 (Generic, ZIP)
5.37k
4.58k (x0.85)
Test#1 (Memory)
3.97k
6.36k (x1.6)
TOTAL
57.86k
53.7k (x0.93)

Multithread

i3-7100

i5-6500
Test#1 (Integers)
54.73k
84.36k (x1.54)
Test#2 (FP)
53.55k
72.91k (x1.36)
Test#3 (Generic, ZIP)
12.93k
16.08k (x1.24)
Test#1 (Memory)
3.6k
6.1k (x1.7)
TOTAL
124.8k
179.44k (x1.44)

Performance/W
i3-7100
i5-6500
Test#1 (Integers)
1073 points/W
1298 points/W
Test#2 (FP)
1050 points/W
1122 points/W
Test#3 (Generic, ZIP)
254 points/W
247 points/W
Test#1 (Memory)
71 points/W
94 points/W
TOTAL
2447 points/W
2761 points/W

Performance/GHz
i3-7100
i5-6500
Test#1 (Integers)
6547 points/GHz
6359 points/GHz
Test#2 (FP)
5893 points/GHz
5521 points/GHz
Test#3 (Generic, ZIP)
1377 points/GHz
1271 points/GHz
Test#1 (Memory)
1019 points/GHz
1766 points/GHz
TOTAL
14836 points/GHz
14917 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