| | | | | | |

Core i5-3210M vs Core 2 Quad Q6600


Description
The i5-3210M is based on Ivy Bridge architecture while the Q6600 is based on Core.

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

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

Specs
CPUID
306a9
6fb
Core
Ivy Bridge
Kentsfield
Architecture
Base frecuency
2.5 GHz
2.4 GHz
Boost frecuency
3.1 GHz
2.4 GHz
Socket
Socket G2 (988B)
LGA 775
Cores/Threads
2 /2
4/4
TDP
35 W
95 W
Cache L1 (d+i)
2x32+2x32 kB
4x32+4x32 kB
Cache L2
2x256 kB
8192 kB
Cache L3
3072 kB
kB
Date
June 2012
July 2007
Mean monothread perf.
24.9k points
8.92k points
Mean multithread perf.
51.73k points
30.64k 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
Q6600
Test#1 (Integers)
8.59k
2.78k (x0.32)
Test#2 (FP)
8.88k
2.49k (x0.28)
Test#3 (Generic, ZIP)
3.59k
2.37k (x0.66)
Test#1 (Memory)
3.45k
1.29k (x0.37)
TOTAL
24.51k
8.92k (x0.36)

Multithread

i5-3210M

Q6600
Test#1 (Integers)
20.18k
10.9k (x0.54)
Test#2 (FP)
19.96k
9.79k (x0.49)
Test#3 (Generic, ZIP)
8.93k
9.11k (x1.02)
Test#1 (Memory)
4.6k
0.84k (x0.18)
TOTAL
53.67k
30.64k (x0.57)

Performance/W
i5-3210M
Q6600
Test#1 (Integers)
577 points/W
115 points/W
Test#2 (FP)
570 points/W
103 points/W
Test#3 (Generic, ZIP)
255 points/W
96 points/W
Test#1 (Memory)
131 points/W
9 points/W
TOTAL
1533 points/W
323 points/W

Performance/GHz
i5-3210M
Q6600
Test#1 (Integers)
2772 points/GHz
1157 points/GHz
Test#2 (FP)
2864 points/GHz
1036 points/GHz
Test#3 (Generic, ZIP)
1157 points/GHz
986 points/GHz
Test#1 (Memory)
1114 points/GHz
539 points/GHz
TOTAL
7908 points/GHz
3718 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