| | | | | | |

Core i5-3210M vs i7-7560U


Description
The i5-3210M is based on Ivy Bridge architecture while the i7-7560U is based on Kaby Lake.

Using the multithread performance as a reference, the i5-3210M gets a score of 51.7 k points while the i7-7560U gets 89 k points.

Summarizing, the i7-7560U is 1.7 times faster than the i5-3210M . To get a proper comparison between both models, take a look to the data shown below.

Specs
CPUID
306a9
806e9
Core
Ivy Bridge
Kaby Lake-U
Architecture
Base frecuency
2.5 GHz
2.4 GHz
Boost frecuency
3.1 GHz
3.8 GHz
Socket
Socket G2 (988B)
BGA 1356
Cores/Threads
2 /2
2/4
TDP
35 W
15 W
Cache L1 (d+i)
2x32+2x32 kB
2x32+2x32 kB
Cache L2
2x256 kB
2x256 kB
Cache L3
3072 kB
4096 kB
Date
June 2012
January 2017
Mean monothread perf.
24.9k points
48.16k points
Mean multithread perf.
51.73k points
97.27k 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-3210M
i7-7560U
Test#1 (Integers)
3.08k
3.56k (x1.15)
Test#2 (FP)
8.58k
12.71k (x1.48)
Test#3 (Generic, ZIP)
3.76k
3.93k (x1.05)
Test#1 (Memory)
3.99k
8.89k (x2.23)
TOTAL
19.42k
29.09k (x1.5)

Multithread

i5-3210M

i7-7560U
Test#1 (Integers)
5.79k
6.34k (x1.09)
Test#2 (FP)
18.77k
29.51k (x1.57)
Test#3 (Generic, ZIP)
8.74k
8.94k (x1.02)
Test#1 (Memory)
4.59k
14.72k (x3.21)
TOTAL
37.89k
59.51k (x1.57)

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-3210M
i7-7560U
Test#1 (Integers)
8.59k
12.78k (x1.49)
Test#2 (FP)
8.88k
18.79k (x2.12)
Test#3 (Generic, ZIP)
3.59k
4.72k (x1.32)
Test#1 (Memory)
3.45k
8.95k (x2.59)
TOTAL
24.51k
45.24k (x1.85)

Multithread

i5-3210M

i7-7560U
Test#1 (Integers)
20.18k
23.04k (x1.14)
Test#2 (FP)
19.96k
40.07k (x2.01)
Test#3 (Generic, ZIP)
8.93k
10.08k (x1.13)
Test#1 (Memory)
4.6k
15.24k (x3.32)
TOTAL
53.67k
88.42k (x1.65)

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-3210M
i7-7560U
Test#1 (Integers)
9.11k
12.88k (x1.41)
Test#2 (FP)
8.88k
20.02k (x2.26)
Test#3 (Generic, ZIP)
3.46k
4.15k (x1.2)
Test#1 (Memory)
3.45k
8.97k (x2.6)
TOTAL
24.9k
46.02k (x1.85)

Multithread

i5-3210M

i7-7560U
Test#1 (Integers)
18.72k
23k (x1.23)
Test#2 (FP)
21.09k
41.21k (x1.95)
Test#3 (Generic, ZIP)
8.38k
9.92k (x1.18)
Test#1 (Memory)
3.54k
14.9k (x4.21)
TOTAL
51.73k
89.03k (x1.72)

Performance/W
i5-3210M
i7-7560U
Test#1 (Integers)
535 points/W
1533 points/W
Test#2 (FP)
603 points/W
2747 points/W
Test#3 (Generic, ZIP)
239 points/W
661 points/W
Test#1 (Memory)
101 points/W
994 points/W
TOTAL
1478 points/W
5935 points/W

Performance/GHz
i5-3210M
i7-7560U
Test#1 (Integers)
2939 points/GHz
3390 points/GHz
Test#2 (FP)
2863 points/GHz
5268 points/GHz
Test#3 (Generic, ZIP)
1117 points/GHz
1092 points/GHz
Test#1 (Memory)
1112 points/GHz
2361 points/GHz
TOTAL
8032 points/GHz
12111 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