| | | | | | |

Core i5-3210M vs Xeon X5675


Description
The i5-3210M is based on Ivy Bridge architecture while the X5675 is based on Westmere.

Using the multithread performance as a reference, the i5-3210M gets a score of 53.7 k points while the X5675 gets 124.9 k points.

Summarizing, the X5675 is 2.3 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
206c2
Core
Ivy Bridge
Westmere-EP
Architecture
Base frecuency
2.5 GHz
3.067 GHz
Boost frecuency
3.1 GHz
3.467 GHz
Socket
Socket G2 (988B)
LGA 1366
Cores/Threads
2 /2
6 /12
TDP
35 W
95 W
Cache L1 (d+i)
2x32+2x32 kB
6x32+6x32 kB
Cache L2
2x256 kB
6x256 kB
Cache L3
3072 kB
12288 kB
Date
June 2012
February 2011
Mean monothread perf.
24.9k points
21.04k points
Mean multithread perf.
51.73k points
124.92k points

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
X5675
Test#1 (Integers)
8.59k
8.77k (x1.02)
Test#2 (FP)
8.88k
5.82k (x0.66)
Test#3 (Generic, ZIP)
3.59k
3.47k (x0.97)
Test#1 (Memory)
3.45k
2.98k (x0.86)
TOTAL
24.51k
21.04k (x0.86)

Multithread

i5-3210M

X5675
Test#1 (Integers)
20.18k
53.23k (x2.64)
Test#2 (FP)
19.96k
39.35k (x1.97)
Test#3 (Generic, ZIP)
8.93k
27.05k (x3.03)
Test#1 (Memory)
4.6k
5.28k (x1.15)
TOTAL
53.67k
124.92k (x2.33)

Performance/W
i5-3210M
X5675
Test#1 (Integers)
577 points/W
560 points/W
Test#2 (FP)
570 points/W
414 points/W
Test#3 (Generic, ZIP)
255 points/W
285 points/W
Test#1 (Memory)
131 points/W
56 points/W
TOTAL
1533 points/W
1315 points/W

Performance/GHz
i5-3210M
X5675
Test#1 (Integers)
2772 points/GHz
2529 points/GHz
Test#2 (FP)
2864 points/GHz
1679 points/GHz
Test#3 (Generic, ZIP)
1157 points/GHz
1001 points/GHz
Test#1 (Memory)
1114 points/GHz
860 points/GHz
TOTAL
7908 points/GHz
6070 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