| | | | | | |

Xeon X5675 vs Core i5-3210M


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

Using the multithread performance as a reference, the X5675 gets a score of 124.9 k points while the i5-3210M gets 53.7 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
206c2
306a9
Core
Westmere-EP
Ivy Bridge
Architecture
Base frecuency
3.067 GHz
2.5 GHz
Boost frecuency
3.467 GHz
3.1 GHz
Socket
LGA 1366
Socket G2 (988B)
Cores/Threads
6 /12
2 /2
TDP
95 W
35 W
Cache L1 (d+i)
6x32+6x32 kB
2x32+2x32 kB
Cache L2
6x256 kB
2x256 kB
Cache L3
12288 kB
3072 kB
Date
February 2011
June 2012
Mean monothread perf.
21.04k points
24.9k points
Mean multithread perf.
124.92k points
51.73k 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
X5675
i5-3210M
Test#1 (Integers)
8.77k
8.59k (x0.98)
Test#2 (FP)
5.82k
8.88k (x1.53)
Test#3 (Generic, ZIP)
3.47k
3.59k (x1.03)
Test#1 (Memory)
2.98k
3.45k (x1.16)
TOTAL
21.04k
24.51k (x1.16)

Multithread

X5675

i5-3210M
Test#1 (Integers)
53.23k
20.18k (x0.38)
Test#2 (FP)
39.35k
19.96k (x0.51)
Test#3 (Generic, ZIP)
27.05k
8.93k (x0.33)
Test#1 (Memory)
5.28k
4.6k (x0.87)
TOTAL
124.92k
53.67k (x0.43)

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

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