| | | | | | |

Core i5-520M vs i3-3217U


Description
The i5-520M is based on Westmere architecture while the i3-3217U is based on Ivy Bridge.

Using the multithread performance as a reference, the i5-520M gets a score of 33.1 k points while the i3-3217U gets 32.8 k points.

Summarizing, the i5-520M is 1 times faster than the i3-3217U . To get a proper comparison between both models, take a look to the data shown below.

Specs
CPUID
20652
306a9
Core
Arrandale
Ivy Bridge
Architecture
Base frecuency
2.4 GHz
1.8 GHz
Boost frecuency
2.933 GHz
1.8 GHz
Socket
FC-PGA 988
BGA1023
Cores/Threads
2/4
2 /2
TDP
35 W
17 W
Cache L1 (d+i)
2x32+2x32 kB
2x32+2x32 kB
Cache L2
2x256 kB
2x256 kB
Cache L3
3072 kB
3072 kB
Date
January 2010
June 2012
Mean monothread perf.
15.93k points
16.09k points
Mean multithread perf.
33.14k points
35.81k 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-520M
i3-3217U
Test#1 (Integers)
6.67k
5.37k (x0.81)
Test#2 (FP)
4.59k
5.25k (x1.14)
Test#3 (Generic, ZIP)
2.49k
2.2k (x0.88)
Test#1 (Memory)
2.18k
2.25k (x1.03)
TOTAL
15.93k
15.08k (x0.95)

Multithread

i5-520M

i3-3217U
Test#1 (Integers)
13.75k
12.46k (x0.91)
Test#2 (FP)
10.03k
12.14k (x1.21)
Test#3 (Generic, ZIP)
6.67k
5.52k (x0.83)
Test#1 (Memory)
2.68k
2.64k (x0.98)
TOTAL
33.14k
32.75k (x0.99)

Performance/W
i5-520M
i3-3217U
Test#1 (Integers)
393 points/W
733 points/W
Test#2 (FP)
287 points/W
714 points/W
Test#3 (Generic, ZIP)
191 points/W
325 points/W
Test#1 (Memory)
77 points/W
155 points/W
TOTAL
947 points/W
1926 points/W

Performance/GHz
i5-520M
i3-3217U
Test#1 (Integers)
2275 points/GHz
2986 points/GHz
Test#2 (FP)
1567 points/GHz
2919 points/GHz
Test#3 (Generic, ZIP)
849 points/GHz
1224 points/GHz
Test#1 (Memory)
742 points/GHz
1250 points/GHz
TOTAL
5433 points/GHz
8378 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