| | | | | | |

Core i3-6006U vs i5-3210M


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

Using the multithread performance as a reference, the i3-6006U gets a score of 49.9 k points while the i5-3210M gets 51.7 k points.

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

Specs
CPUID
406e3
306a9
Core
Skylake-U
Ivy Bridge
Architecture
Base frecuency
2 GHz
2.5 GHz
Boost frecuency
2 GHz
3.1 GHz
Socket
BGA1356
Socket G2 (988B)
Cores/Threads
2/4
2 /2
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
November 2016
June 2012
Mean monothread perf.
31.3k points
24.9k points
Mean multithread perf.
68.38k points
51.73k 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
i3-6006U
i5-3210M
Test#1 (Integers)
2.02k
3.08k (x1.53)
Test#2 (FP)
8.2k
8.58k (x1.05)
Test#3 (Generic, ZIP)
2.63k
3.76k (x1.43)
Test#1 (Memory)
3.92k
3.99k (x1.02)
TOTAL
16.77k
19.42k (x1.16)

Multithread

i3-6006U

i5-3210M
Test#1 (Integers)
3.83k
5.79k (x1.51)
Test#2 (FP)
17.17k
18.77k (x1.09)
Test#3 (Generic, ZIP)
5.77k
8.74k (x1.51)
Test#1 (Memory)
3.62k
4.59k (x1.27)
TOTAL
30.39k
37.89k (x1.25)

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
i3-6006U
i5-3210M
Test#1 (Integers)
7.28k
8.59k (x1.18)
Test#2 (FP)
10.51k
8.88k (x0.84)
Test#3 (Generic, ZIP)
2.81k
3.59k (x1.28)
Test#1 (Memory)
2.88k
3.45k (x1.2)
TOTAL
23.48k
24.51k (x1.04)

Multithread

i3-6006U

i5-3210M
Test#1 (Integers)
14.98k
20.18k (x1.35)
Test#2 (FP)
23.68k
19.96k (x0.84)
Test#3 (Generic, ZIP)
6.37k
8.93k (x1.4)
Test#1 (Memory)
2.43k
4.6k (x1.89)
TOTAL
47.46k
53.67k (x1.13)

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
i3-6006U
i5-3210M
Test#1 (Integers)
7.34k
9.11k (x1.24)
Test#2 (FP)
11.37k
8.88k (x0.78)
Test#3 (Generic, ZIP)
2.74k
3.46k (x1.26)
Test#1 (Memory)
3.08k
3.45k (x1.12)
TOTAL
24.53k
24.9k (x1.02)

Multithread

i3-6006U

i5-3210M
Test#1 (Integers)
15.32k
18.72k (x1.22)
Test#2 (FP)
25.61k
21.09k (x0.82)
Test#3 (Generic, ZIP)
6.36k
8.38k (x1.32)
Test#1 (Memory)
2.58k
3.54k (x1.37)
TOTAL
49.87k
51.73k (x1.04)

Performance/W
i3-6006U
i5-3210M
Test#1 (Integers)
1022 points/W
535 points/W
Test#2 (FP)
1707 points/W
603 points/W
Test#3 (Generic, ZIP)
424 points/W
239 points/W
Test#1 (Memory)
172 points/W
101 points/W
TOTAL
3325 points/W
1478 points/W

Performance/GHz
i3-6006U
i5-3210M
Test#1 (Integers)
3670 points/GHz
2939 points/GHz
Test#2 (FP)
5683 points/GHz
2863 points/GHz
Test#3 (Generic, ZIP)
1372 points/GHz
1117 points/GHz
Test#1 (Memory)
1540 points/GHz
1112 points/GHz
TOTAL
12265 points/GHz
8032 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