| | | | | | |

Core i3-3217U vs i5-520M


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

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

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

Specs
CPUID
306a9
20655
Core
Ivy Bridge
Arrandale
Architecture
Base frecuency
1.8 GHz
2.4 GHz
Boost frecuency
1.8 GHz
2.933 GHz
Socket
BGA1023
FC-PGA 988
Cores/Threads
2 /2
2/4
TDP
17 W
35 W
Cache L1 (d+i)
2x32+2x32 kB
2x32+2x32 kB
Cache L2
2x256 kB
2x256 kB
Cache L3
3072 kB
3072 kB
Date
June 2012
January 2010
Mean monothread perf.
16.09k points
13.1k points
Mean multithread perf.
35.81k points
26.27k 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
i3-3217U
i5-520M
Test#1 (Integers)
5.37k
5.41k (x1.01)
Test#2 (FP)
5.25k
3.69k (x0.7)
Test#3 (Generic, ZIP)
2.2k
2.12k (x0.96)
Test#1 (Memory)
2.25k
1.88k (x0.84)
TOTAL
15.08k
13.1k (x0.87)

Multithread

i3-3217U

i5-520M
Test#1 (Integers)
12.46k
10.7k (x0.86)
Test#2 (FP)
12.14k
7.91k (x0.65)
Test#3 (Generic, ZIP)
5.52k
5.08k (x0.92)
Test#1 (Memory)
2.64k
2.58k (x0.98)
TOTAL
32.75k
26.27k (x0.8)

Performance/W
i3-3217U
i5-520M
Test#1 (Integers)
733 points/W
306 points/W
Test#2 (FP)
714 points/W
226 points/W
Test#3 (Generic, ZIP)
325 points/W
145 points/W
Test#1 (Memory)
155 points/W
74 points/W
TOTAL
1926 points/W
751 points/W

Performance/GHz
i3-3217U
i5-520M
Test#1 (Integers)
2986 points/GHz
1844 points/GHz
Test#2 (FP)
2919 points/GHz
1259 points/GHz
Test#3 (Generic, ZIP)
1224 points/GHz
723 points/GHz
Test#1 (Memory)
1250 points/GHz
641 points/GHz
TOTAL
8378 points/GHz
4466 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