| | | | | | |

Core i3-7100U vs i5-3570K


Description
The i3-7100U is based on Kaby Lake architecture while the i5-3570K is based on Ivy Bridge.

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

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

Specs
CPUID
806e9
306a9
Core
Kaby Lake-U
Ivy Bridge
Architecture
Base frecuency
2.4 GHz
3.4 GHz
Boost frecuency
2.4 GHz
3.8 GHz
Socket
BGA 1356
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
August 2016
April 2012
Mean monothread perf.
33.38k points
34.57k points
Mean multithread perf.
79.6k 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-7100U
i5-3570K
Test#1 (Integers)
2.41k
3.85k (x1.6)
Test#2 (FP)
9.77k
10.72k (x1.1)
Test#3 (Generic, ZIP)
3.13k
4.83k (x1.54)
Test#1 (Memory)
3.55k
5.21k (x1.47)
TOTAL
18.86k
24.6k (x1.3)

Multithread

i3-7100U

i5-3570K
Test#1 (Integers)
5k
14.34k (x2.87)
Test#2 (FP)
21.48k
40.2k (x1.87)
Test#3 (Generic, ZIP)
7.39k
17.91k (x2.42)
Test#1 (Memory)
3.18k
7.05k (x2.22)
TOTAL
37.05k
79.5k (x2.15)

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-7100U
i5-3570K
Test#1 (Integers)
8.66k
12.78k (x1.48)
Test#2 (FP)
12.31k
11.69k (x0.95)
Test#3 (Generic, ZIP)
3.28k
5.01k (x1.53)
Test#1 (Memory)
3.92k
5.19k (x1.32)
TOTAL
28.16k
34.66k (x1.23)

Multithread

i3-7100U

i5-3570K
Test#1 (Integers)
17.87k
48.18k (x2.7)
Test#2 (FP)
28.59k
43.19k (x1.51)
Test#3 (Generic, ZIP)
7.68k
18.37k (x2.39)
Test#1 (Memory)
3.15k
7.03k (x2.24)
TOTAL
57.28k
116.78k (x2.04)

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-7100U
i5-3570K
Test#1 (Integers)
8.76k
12.55k (x1.43)
Test#2 (FP)
13.49k
12.14k (x0.9)
Test#3 (Generic, ZIP)
3.21k
4.9k (x1.53)
Test#1 (Memory)
3.9k
4.98k (x1.28)
TOTAL
29.36k
34.57k (x1.18)

Multithread

i3-7100U

i5-3570K
Test#1 (Integers)
18.33k
47.53k (x2.59)
Test#2 (FP)
31.08k
46.16k (x1.49)
Test#3 (Generic, ZIP)
7.5k
18.36k (x2.45)
Test#1 (Memory)
3.61k
8.1k (x2.25)
TOTAL
60.52k
120.16k (x1.99)

Performance/W
i3-7100U
i5-3570K
Test#1 (Integers)
1222 points/W
617 points/W
Test#2 (FP)
2072 points/W
599 points/W
Test#3 (Generic, ZIP)
500 points/W
238 points/W
Test#1 (Memory)
240 points/W
105 points/W
TOTAL
4035 points/W
1560 points/W

Performance/GHz
i3-7100U
i5-3570K
Test#1 (Integers)
3652 points/GHz
3303 points/GHz
Test#2 (FP)
5622 points/GHz
3194 points/GHz
Test#3 (Generic, ZIP)
1337 points/GHz
1288 points/GHz
Test#1 (Memory)
1624 points/GHz
1310 points/GHz
TOTAL
12235 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