| | | | | | |

Core i3-6100U vs i5-3570K


Description
The i3-6100U is based on Skylake architecture while the i5-3570K is based on Ivy Bridge.

Using the multithread performance as a reference, the i3-6100U gets a score of 56.7 k points while the i5-3570K gets 120.2 k points.

Summarizing, the i5-3570K is 2.1 times faster than the i3-6100U. To get a proper comparison between both models, take a look to the data shown below.

Specs
CPUID
406e3
306a9
Core
Skylake-U
Ivy Bridge
Architecture
Base frecuency
2.3 GHz
3.4 GHz
Boost frecuency
2.3 GHz
3.8 GHz
Socket
BGA1356
LGA 1155
Cores/Threads
2/4
4/4
TDP
15 W
77 W
Cache L1 (d+i)
2x32+2x32 kB
4x32+x4x32 kB
Cache L2
2x256 kB
4x256 kB
Cache L3
3072 kB
6144 kB
Date
September 2015
April 2012
Mean monothread perf.
30.73k points
34.57k points
Mean multithread perf.
69.94k points
120.16k 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-6100U
i5-3570K
Test#1 (Integers)
2.27k
3.85k (x1.69)
Test#2 (FP)
9.18k
10.72k (x1.17)
Test#3 (Generic, ZIP)
2.97k
4.83k (x1.62)
Test#1 (Memory)
3.79k
5.21k (x1.38)
TOTAL
18.21k
24.6k (x1.35)

Multithread

i3-6100U

i5-3570K
Test#1 (Integers)
4.79k
14.34k (x3)
Test#2 (FP)
23.04k
40.2k (x1.74)
Test#3 (Generic, ZIP)
7.55k
17.91k (x2.37)
Test#1 (Memory)
3.86k
7.05k (x1.83)
TOTAL
39.24k
79.5k (x2.03)

SSE3 optimized benchmark
The benchmark in mode I (SSE) is optimized for the use of SIMD instructions with 128 bits register and the SSE set up to version 3. Nearly every modern CPU has support for this mode.
Monothread
i3-6100U
i5-3570K
Test#1 (Integers)
7.99k
12.78k (x1.6)
Test#2 (FP)
11.82k
11.69k (x0.99)
Test#3 (Generic, ZIP)
2.97k
5.01k (x1.69)
Test#1 (Memory)
3.75k
5.19k (x1.38)
TOTAL
26.52k
34.66k (x1.31)

Multithread

i3-6100U

i5-3570K
Test#1 (Integers)
15.44k
48.18k (x3.12)
Test#2 (FP)
23.79k
43.19k (x1.82)
Test#3 (Generic, ZIP)
6.93k
18.37k (x2.65)
Test#1 (Memory)
4.03k
7.03k (x1.74)
TOTAL
50.19k
116.78k (x2.33)

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-6100U
i5-3570K
Test#1 (Integers)
8.06k
12.55k (x1.56)
Test#2 (FP)
12.85k
12.14k (x0.94)
Test#3 (Generic, ZIP)
3.14k
4.9k (x1.56)
Test#1 (Memory)
4.01k
4.98k (x1.24)
TOTAL
28.06k
34.57k (x1.23)

Multithread

i3-6100U

i5-3570K
Test#1 (Integers)
16.58k
47.53k (x2.87)
Test#2 (FP)
28.88k
46.16k (x1.6)
Test#3 (Generic, ZIP)
7.38k
18.36k (x2.49)
Test#1 (Memory)
3.82k
8.1k (x2.12)
TOTAL
56.66k
120.16k (x2.12)

Performance/W
i3-6100U
i5-3570K
Test#1 (Integers)
1105 points/W
617 points/W
Test#2 (FP)
1925 points/W
599 points/W
Test#3 (Generic, ZIP)
492 points/W
238 points/W
Test#1 (Memory)
254 points/W
105 points/W
TOTAL
3777 points/W
1560 points/W

Performance/GHz
i3-6100U
i5-3570K
Test#1 (Integers)
3506 points/GHz
3303 points/GHz
Test#2 (FP)
5587 points/GHz
3194 points/GHz
Test#3 (Generic, ZIP)
1366 points/GHz
1288 points/GHz
Test#1 (Memory)
1742 points/GHz
1310 points/GHz
TOTAL
12201 points/GHz
9096 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