| | | | | | |

Core i5-3210M vs i5-7200U


Description
The i5-3210M is based on Ivy Bridge architecture while the i5-7200U 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 i5-7200U gets 80.2 k points.

Summarizing, the i5-7200U is 1.6 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.5 GHz
Boost frecuency
3.1 GHz
3.1 GHz
Socket
Socket G2 (988B)
BGA1356
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
3072 kB
Date
June 2012
August 2016
Mean monothread perf.
24.9k points
44.94k points
Mean multithread perf.
51.73k points
97.52k 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
i5-7200U
Test#1 (Integers)
3.08k
3.15k (x1.02)
Test#2 (FP)
8.58k
12.85k (x1.5)
Test#3 (Generic, ZIP)
3.76k
4.14k (x1.1)
Test#1 (Memory)
3.99k
5.21k (x1.31)
TOTAL
19.42k
25.36k (x1.31)

Multithread

i5-3210M

i5-7200U
Test#1 (Integers)
5.79k
6.28k (x1.09)
Test#2 (FP)
18.77k
29.27k (x1.56)
Test#3 (Generic, ZIP)
8.74k
9.31k (x1.06)
Test#1 (Memory)
4.59k
4.71k (x1.03)
TOTAL
37.89k
49.56k (x1.31)

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
i5-7200U
Test#1 (Integers)
8.59k
11.39k (x1.33)
Test#2 (FP)
8.88k
16.47k (x1.85)
Test#3 (Generic, ZIP)
3.59k
4.36k (x1.22)
Test#1 (Memory)
3.45k
5.21k (x1.51)
TOTAL
24.51k
37.43k (x1.53)

Multithread

i5-3210M

i5-7200U
Test#1 (Integers)
20.18k
23.57k (x1.17)
Test#2 (FP)
19.96k
37.4k (x1.87)
Test#3 (Generic, ZIP)
8.93k
10.15k (x1.14)
Test#1 (Memory)
4.6k
4.78k (x1.04)
TOTAL
53.67k
75.9k (x1.41)

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
i5-7200U
Test#1 (Integers)
9.11k
11.36k (x1.25)
Test#2 (FP)
8.88k
17.26k (x1.95)
Test#3 (Generic, ZIP)
3.46k
4.03k (x1.16)
Test#1 (Memory)
3.45k
4.77k (x1.38)
TOTAL
24.9k
37.42k (x1.5)

Multithread

i5-3210M

i5-7200U
Test#1 (Integers)
18.72k
24.08k (x1.29)
Test#2 (FP)
21.09k
41.23k (x1.96)
Test#3 (Generic, ZIP)
8.38k
10.19k (x1.22)
Test#1 (Memory)
3.54k
4.72k (x1.33)
TOTAL
51.73k
80.22k (x1.55)

Performance/W
i5-3210M
i5-7200U
Test#1 (Integers)
535 points/W
1605 points/W
Test#2 (FP)
603 points/W
2749 points/W
Test#3 (Generic, ZIP)
239 points/W
679 points/W
Test#1 (Memory)
101 points/W
315 points/W
TOTAL
1478 points/W
5348 points/W

Performance/GHz
i5-3210M
i5-7200U
Test#1 (Integers)
2939 points/GHz
3666 points/GHz
Test#2 (FP)
2863 points/GHz
5569 points/GHz
Test#3 (Generic, ZIP)
1117 points/GHz
1300 points/GHz
Test#1 (Memory)
1112 points/GHz
1537 points/GHz
TOTAL
8032 points/GHz
12072 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