| | | | | | |

Core i3-540 vs i5-3210M


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

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

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

Specs
CPUID
20655
306a9
Core
Clarkdale
Ivy Bridge
Architecture
Base frecuency
3.067 GHz
2.5 GHz
Boost frecuency
3.067 GHz
3.1 GHz
Socket
LGA 1156
Socket G2 (988B)
Cores/Threads
2/2
2 /2
TDP
73 W
35 W
Cache L1 (d+i)
2x32+2x32 kB
2x32+2x32 kB
Cache L2
2x256 kB
2x256 kB
Cache L3
4096 kB
3072 kB
Date
January 2010
June 2012
Mean monothread perf.
18.27k points
24.9k points
Mean multithread perf.
38.86k 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
i3-540
i5-3210M
Test#1 (Integers)
7.65k
8.59k (x1.12)
Test#2 (FP)
5.14k
8.88k (x1.73)
Test#3 (Generic, ZIP)
3.06k
3.59k (x1.17)
Test#1 (Memory)
2.42k
3.45k (x1.43)
TOTAL
18.27k
24.51k (x1.34)

Multithread

i3-540

i5-3210M
Test#1 (Integers)
16.21k
20.18k (x1.24)
Test#2 (FP)
12.04k
19.96k (x1.66)
Test#3 (Generic, ZIP)
8.28k
8.93k (x1.08)
Test#1 (Memory)
2.33k
4.6k (x1.98)
TOTAL
38.86k
53.67k (x1.38)

Performance/W
i3-540
i5-3210M
Test#1 (Integers)
222 points/W
577 points/W
Test#2 (FP)
165 points/W
570 points/W
Test#3 (Generic, ZIP)
113 points/W
255 points/W
Test#1 (Memory)
32 points/W
131 points/W
TOTAL
532 points/W
1533 points/W

Performance/GHz
i3-540
i5-3210M
Test#1 (Integers)
2494 points/GHz
2772 points/GHz
Test#2 (FP)
1676 points/GHz
2864 points/GHz
Test#3 (Generic, ZIP)
999 points/GHz
1157 points/GHz
Test#1 (Memory)
789 points/GHz
1114 points/GHz
TOTAL
5958 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