| | | | | | |

Core i5-3210M vs Xeon E5-2670 v3


Description
The i5-3210M is based on Ivy Bridge architecture while the E5-2670 v3 is based on Haswell.

Using the multithread performance as a reference, the i5-3210M gets a score of 51.7 k points while the E5-2670 v3 gets 338.7 k points.

Summarizing, the E5-2670 v3 is 6.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
306f2
Core
Ivy Bridge
Haswell-EP
Architecture
Base frecuency
2.5 GHz
2.3 GHz
Boost frecuency
3.1 GHz
3.1 GHz
Socket
Socket G2 (988B)
LGA 2011-3
Cores/Threads
2 /2
12/24
TDP
35 W
120 W
Cache L1 (d+i)
2x32+2x32 kB
12x32+12x32 kB
Cache L2
2x256 kB
12x256 kB
Cache L3
3072 kB
30720 kB
Date
June 2012
September 2014
Mean monothread perf.
24.9k points
36.41k points
Mean multithread perf.
51.73k points
452.9k 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
E5-2670 v3
Test#1 (Integers)
3.08k
3.52k (x1.14)
Test#2 (FP)
8.58k
8.68k (x1.01)
Test#3 (Generic, ZIP)
3.76k
2.83k (x0.75)
Test#1 (Memory)
3.99k
3.13k (x0.78)
TOTAL
19.42k
18.17k (x0.94)

Multithread

i5-3210M

E5-2670 v3
Test#1 (Integers)
5.79k
32.7k (x5.65)
Test#2 (FP)
18.77k
105.18k (x5.6)
Test#3 (Generic, ZIP)
8.74k
35.18k (x4.02)
Test#1 (Memory)
4.59k
9.54k (x2.08)
TOTAL
37.89k
182.59k (x4.82)

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
E5-2670 v3
Test#1 (Integers)
8.59k
11.08k (x1.29)
Test#2 (FP)
8.88k
9.57k (x1.08)
Test#3 (Generic, ZIP)
3.59k
3.18k (x0.89)
Test#1 (Memory)
3.45k
3.28k (x0.95)
TOTAL
24.51k
27.11k (x1.11)

Multithread

i5-3210M

E5-2670 v3
Test#1 (Integers)
20.18k
139.07k (x6.89)
Test#2 (FP)
19.96k
133.47k (x6.69)
Test#3 (Generic, ZIP)
8.93k
46.6k (x5.22)
Test#1 (Memory)
4.6k
6.65k (x1.45)
TOTAL
53.67k
325.78k (x6.07)

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
E5-2670 v3
Test#1 (Integers)
9.11k
11.18k (x1.23)
Test#2 (FP)
8.88k
10.06k (x1.13)
Test#3 (Generic, ZIP)
3.46k
3.21k (x0.93)
Test#1 (Memory)
3.45k
3.12k (x0.91)
TOTAL
24.9k
27.57k (x1.11)

Multithread

i5-3210M

E5-2670 v3
Test#1 (Integers)
18.72k
140.98k (x7.53)
Test#2 (FP)
21.09k
145.37k (x6.89)
Test#3 (Generic, ZIP)
8.38k
45.62k (x5.45)
Test#1 (Memory)
3.54k
6.75k (x1.91)
TOTAL
51.73k
338.73k (x6.55)

Performance/W
i5-3210M
E5-2670 v3
Test#1 (Integers)
535 points/W
1175 points/W
Test#2 (FP)
603 points/W
1211 points/W
Test#3 (Generic, ZIP)
239 points/W
380 points/W
Test#1 (Memory)
101 points/W
56 points/W
TOTAL
1478 points/W
2823 points/W

Performance/GHz
i5-3210M
E5-2670 v3
Test#1 (Integers)
2939 points/GHz
3607 points/GHz
Test#2 (FP)
2863 points/GHz
3245 points/GHz
Test#3 (Generic, ZIP)
1117 points/GHz
1035 points/GHz
Test#1 (Memory)
1112 points/GHz
1007 points/GHz
TOTAL
8032 points/GHz
8894 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