| | | | | | |

Core i5-3330 vs i5-7400


Description
The i5-3330 is based on Ivy Bridge architecture while the i5-7400 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 i5-7400 gets 145.2 k points.

Summarizing, the i5-7400 is 1.4 times faster than the i5-3330 . 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 GHz
Boost frecuency
3.2 GHz
3.5 GHz
Socket
LGA 1155
LGA 1151
Cores/Threads
4/4
4/4
TDP
77 W
65 W
Cache L1 (d+i)
32+32 kB
4x32+4x32 kB
Cache L2
256 kB
4x256 kB
Cache L3
6144 kB
6144 kB
Date
September 2012
September 2016
Mean monothread perf.
29.84k points
52.69k points
Mean multithread perf.
104.78k points
173.7k 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
i5-7400
Test#1 (Integers)
10.85k
12.72k (x1.17)
Test#2 (FP)
10.47k
19.3k (x1.84)
Test#3 (Generic, ZIP)
4.21k
4.76k (x1.13)
Test#1 (Memory)
4.31k
8.73k (x2.03)
TOTAL
29.84k
45.52k (x1.53)

Multithread

i5-3330

i5-7400
Test#1 (Integers)
41.77k
47.95k (x1.15)
Test#2 (FP)
40.2k
71.98k (x1.79)
Test#3 (Generic, ZIP)
16.11k
17.22k (x1.07)
Test#1 (Memory)
6.7k
8.03k (x1.2)
TOTAL
104.78k
145.18k (x1.39)

Performance/W
i5-3330
i5-7400
Test#1 (Integers)
542 points/W
738 points/W
Test#2 (FP)
522 points/W
1107 points/W
Test#3 (Generic, ZIP)
209 points/W
265 points/W
Test#1 (Memory)
87 points/W
123 points/W
TOTAL
1361 points/W
2233 points/W

Performance/GHz
i5-3330
i5-7400
Test#1 (Integers)
3390 points/GHz
3635 points/GHz
Test#2 (FP)
3272 points/GHz
5514 points/GHz
Test#3 (Generic, ZIP)
1316 points/GHz
1361 points/GHz
Test#1 (Memory)
1347 points/GHz
2495 points/GHz
TOTAL
9325 points/GHz
13006 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