| | | | | | |

Core i5-3210M vs i7-6500U


Description
The i5-3210M is based on Ivy Bridge architecture while the i7-6500U is based on Skylake.

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

Summarizing, the i7-6500U is 1.5 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
406e3
Core
Ivy Bridge
Skylake-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
4096 kB
Cache L3
3072 kB
kB
Date
June 2012
September 2015
Mean monothread perf.
24.9k points
46.25k 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
i7-6500U
Test#1 (Integers)
3.08k
2.98k (x0.97)
Test#2 (FP)
8.58k
12.19k (x1.42)
Test#3 (Generic, ZIP)
3.76k
3.91k (x1.04)
Test#1 (Memory)
3.99k
5.3k (x1.33)
TOTAL
19.42k
24.37k (x1.26)

Multithread

i5-3210M

i7-6500U
Test#1 (Integers)
5.79k
6.1k (x1.05)
Test#2 (FP)
18.77k
28.73k (x1.53)
Test#3 (Generic, ZIP)
8.74k
9.56k (x1.09)
Test#1 (Memory)
4.59k
6.71k (x1.46)
TOTAL
37.89k
51.09k (x1.35)

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-6500U
Test#1 (Integers)
8.59k
11.11k (x1.29)
Test#2 (FP)
8.88k
15.97k (x1.8)
Test#3 (Generic, ZIP)
3.59k
4.25k (x1.18)
Test#1 (Memory)
3.45k
5.66k (x1.64)
TOTAL
24.51k
36.99k (x1.51)

Multithread

i5-3210M

i7-6500U
Test#1 (Integers)
20.18k
23.1k (x1.14)
Test#2 (FP)
19.96k
36.73k (x1.84)
Test#3 (Generic, ZIP)
8.93k
9.99k (x1.12)
Test#1 (Memory)
4.6k
7k (x1.52)
TOTAL
53.67k
76.82k (x1.43)

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-6500U
Test#1 (Integers)
9.11k
11.09k (x1.22)
Test#2 (FP)
8.88k
17.1k (x1.93)
Test#3 (Generic, ZIP)
3.46k
4.12k (x1.19)
Test#1 (Memory)
3.45k
5.58k (x1.62)
TOTAL
24.9k
37.9k (x1.52)

Multithread

i5-3210M

i7-6500U
Test#1 (Integers)
18.72k
23.3k (x1.24)
Test#2 (FP)
21.09k
38.52k (x1.83)
Test#3 (Generic, ZIP)
8.38k
9.95k (x1.19)
Test#1 (Memory)
3.54k
6.95k (x1.96)
TOTAL
51.73k
78.72k (x1.52)

Performance/W
i5-3210M
i7-6500U
Test#1 (Integers)
535 points/W
1553 points/W
Test#2 (FP)
603 points/W
2568 points/W
Test#3 (Generic, ZIP)
239 points/W
663 points/W
Test#1 (Memory)
101 points/W
463 points/W
TOTAL
1478 points/W
5248 points/W

Performance/GHz
i5-3210M
i7-6500U
Test#1 (Integers)
2939 points/GHz
3579 points/GHz
Test#2 (FP)
2863 points/GHz
5516 points/GHz
Test#3 (Generic, ZIP)
1117 points/GHz
1330 points/GHz
Test#1 (Memory)
1112 points/GHz
1801 points/GHz
TOTAL
8032 points/GHz
12225 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