| | | | | | |

Core i5-3210M vs i5-4460


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

Using the multithread performance as a reference, the i5-3210M gets a score of 51.7 k points while the i5-4460 gets 112.4 k points.

Summarizing, the i5-4460 is 2.2 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
306c3
Core
Ivy Bridge
Haswell
Architecture
Base frecuency
2.5 GHz
3.2 GHz
Boost frecuency
3.1 GHz
3.4 GHz
Socket
Socket G2 (988B)
LGA1150
Cores/Threads
2 /2
4/4
TDP
35 W
84 W
Cache L1 (d+i)
2x32+2x32 kB
4x32+4x32 kB
Cache L2
2x256 kB
4x256 kB
Cache L3
3072 kB
6144 kB
Date
June 2012
May 2014
Mean monothread perf.
24.9k points
39.53k points
Mean multithread perf.
51.73k points
140.27k points

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
i5-4460
Test#1 (Integers)
9.11k
12.12k (x1.33)
Test#2 (FP)
8.88k
10.69k (x1.2)
Test#3 (Generic, ZIP)
3.46k
4.71k (x1.36)
Test#1 (Memory)
3.45k
3.87k (x1.12)
TOTAL
24.9k
31.39k (x1.26)

Multithread

i5-3210M

i5-4460
Test#1 (Integers)
18.72k
45.75k (x2.44)
Test#2 (FP)
21.09k
42.71k (x2.03)
Test#3 (Generic, ZIP)
8.38k
17.81k (x2.13)
Test#1 (Memory)
3.54k
6.08k (x1.72)
TOTAL
51.73k
112.35k (x2.17)

Performance/W
i5-3210M
i5-4460
Test#1 (Integers)
535 points/W
545 points/W
Test#2 (FP)
603 points/W
508 points/W
Test#3 (Generic, ZIP)
239 points/W
212 points/W
Test#1 (Memory)
101 points/W
72 points/W
TOTAL
1478 points/W
1338 points/W

Performance/GHz
i5-3210M
i5-4460
Test#1 (Integers)
2939 points/GHz
3565 points/GHz
Test#2 (FP)
2863 points/GHz
3143 points/GHz
Test#3 (Generic, ZIP)
1117 points/GHz
1385 points/GHz
Test#1 (Memory)
1112 points/GHz
1139 points/GHz
TOTAL
8032 points/GHz
9232 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