| | | | | | |

Core i5-3330 vs i3-7100


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

Using the multithread performance as a reference, the i5-3330 gets a score of 104.8 k points while the i3-7100 gets 100.1 k points.

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

Specs
CPUID
306a9
906e9
Core
Ivy Bridge
Kaby Lake-S
Architecture
Base frecuency
3 GHz
3.9 GHz
Boost frecuency
3.2 GHz
3.9 GHz
Socket
LGA 1155
LGA 1151
Cores/Threads
4/4
2/4
TDP
77 W
51 W
Cache L1 (d+i)
32+32 kB
2x32+2x32 kB
Cache L2
256 kB
2x256 kB
Cache L3
6144 kB
3072 kB
Date
September 2012
January 2017
Mean monothread perf.
29.84k points
57.86k points
Mean multithread perf.
104.78k points
124.8k points

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-3330
i3-7100
Test#1 (Integers)
10.85k
14.41k (x1.33)
Test#2 (FP)
10.47k
22.38k (x2.14)
Test#3 (Generic, ZIP)
4.21k
5.45k (x1.29)
Test#1 (Memory)
4.31k
4.96k (x1.15)
TOTAL
29.84k
47.21k (x1.58)

Multithread

i5-3330

i3-7100
Test#1 (Integers)
41.77k
30.48k (x0.73)
Test#2 (FP)
40.2k
52.08k (x1.3)
Test#3 (Generic, ZIP)
16.11k
12.97k (x0.81)
Test#1 (Memory)
6.7k
4.56k (x0.68)
TOTAL
104.78k
100.1k (x0.96)

Performance/W
i5-3330
i3-7100
Test#1 (Integers)
542 points/W
598 points/W
Test#2 (FP)
522 points/W
1021 points/W
Test#3 (Generic, ZIP)
209 points/W
254 points/W
Test#1 (Memory)
87 points/W
89 points/W
TOTAL
1361 points/W
1963 points/W

Performance/GHz
i5-3330
i3-7100
Test#1 (Integers)
3390 points/GHz
3695 points/GHz
Test#2 (FP)
3272 points/GHz
5739 points/GHz
Test#3 (Generic, ZIP)
1316 points/GHz
1399 points/GHz
Test#1 (Memory)
1347 points/GHz
1273 points/GHz
TOTAL
9325 points/GHz
12105 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