| | | | | | |

Core i5-7300U vs i5-3320M


Description
The i5-7300U is based on Kaby Lake architecture while the i5-3320M is based on Ivy Bridge.

Using the multithread performance as a reference, the i5-7300U gets a score of 84.8 k points while the i5-3320M gets 58.8 k points.

Summarizing, the i5-7300U is 1.4 times faster than the i5-3320M . 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.6 GHz
2.6 GHz
Boost frecuency
3.5 GHz
3.3 GHz
Socket
BGA1356
BGA1023
Cores/Threads
2/4
2/4
TDP
15 W
35 W
Cache L1 (d+i)
2x32+2x32 kB
2x32+2x32 kB
Cache L2
2x256 kB
2x256 kB
Cache L3
3072 kB
3072 kB
Date
January 2017
June 2012
Mean monothread perf.
48.25k points
29.22k points
Mean multithread perf.
109.1k points
58.81k 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
i5-7300U
i5-3320M
Test#1 (Integers)
3.11k
3.21k (x1.03)
Test#2 (FP)
12.24k
9.05k (x0.74)
Test#3 (Generic, ZIP)
4.1k
3.94k (x0.96)
Test#1 (Memory)
4.96k
3.93k (x0.79)
TOTAL
24.41k
20.13k (x0.82)

Multithread

i5-7300U

i5-3320M
Test#1 (Integers)
6.98k
6.08k (x0.87)
Test#2 (FP)
32.05k
19.02k (x0.59)
Test#3 (Generic, ZIP)
10.82k
8.85k (x0.82)
Test#1 (Memory)
5.52k
3.98k (x0.72)
TOTAL
55.36k
37.93k (x0.69)

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
i5-7300U
i5-3320M
Test#1 (Integers)
9.96k
10.89k (x1.09)
Test#2 (FP)
15.11k
9.77k (x0.65)
Test#3 (Generic, ZIP)
3.87k
3.98k (x1.03)
Test#1 (Memory)
4.54k
3.77k (x0.83)
TOTAL
33.47k
28.4k (x0.85)

Multithread

i5-7300U

i5-3320M
Test#1 (Integers)
25.26k
20.23k (x0.8)
Test#2 (FP)
40.6k
20.83k (x0.51)
Test#3 (Generic, ZIP)
11.24k
9.49k (x0.84)
Test#1 (Memory)
5.83k
4.04k (x0.69)
TOTAL
82.94k
54.6k (x0.66)

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-7300U
i5-3320M
Test#1 (Integers)
9.85k
10.64k (x1.08)
Test#2 (FP)
17.37k
10.53k (x0.61)
Test#3 (Generic, ZIP)
3.98k
4.07k (x1.02)
Test#1 (Memory)
5.11k
3.97k (x0.78)
TOTAL
36.31k
29.22k (x0.8)

Multithread

i5-7300U

i5-3320M
Test#1 (Integers)
25.37k
21.27k (x0.84)
Test#2 (FP)
43.43k
23.93k (x0.55)
Test#3 (Generic, ZIP)
10.62k
9.48k (x0.89)
Test#1 (Memory)
5.4k
4.12k (x0.76)
TOTAL
84.82k
58.81k (x0.69)

Performance/W
i5-7300U
i5-3320M
Test#1 (Integers)
1691 points/W
608 points/W
Test#2 (FP)
2896 points/W
684 points/W
Test#3 (Generic, ZIP)
708 points/W
271 points/W
Test#1 (Memory)
360 points/W
118 points/W
TOTAL
5655 points/W
1680 points/W

Performance/GHz
i5-7300U
i5-3320M
Test#1 (Integers)
2816 points/GHz
3225 points/GHz
Test#2 (FP)
4962 points/GHz
3191 points/GHz
Test#3 (Generic, ZIP)
1137 points/GHz
1234 points/GHz
Test#1 (Memory)
1461 points/GHz
1203 points/GHz
TOTAL
10376 points/GHz
8853 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