| | | | | | |

Pentium E5500 vs Core i3-3217U


Description
The E5500 is based on Core architecture while the i3-3217U is based on Ivy Bridge.

Using the multithread performance as a reference, the E5500 gets a score of 20.7 k points while the i3-3217U gets 22.9 k points.

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

Specs
CPUID
1067a
306a9
Core
Wolfdale
Ivy Bridge
Architecture
Base frecuency
2.8 GHz
1.8 GHz
Socket
LGA 775
BGA1023
Cores/Threads
2/2
2 /2
TDP
65 W
17 W
Cache L1 (d+i)
32+32 kB
2x32+2x32 kB
Cache L2
2048 kB
2x256 kB
Cache L3
0 kB
3072 kB
Date
April 2010
June 2012
Mean monothread perf.
12.77k points
16.09k points
Mean multithread perf.
20.69k points
35.81k points

Non-optimized benchmark
The benchmark in Mode 0 (FPU) measures cpu performance with non-optimized software. It uses the basic µinstructions from the i386 architecture with the i387 floating point unit. This mode is compatible with all CPUs so it's practical to compare very different CPUs
Monothread
E5500
i3-3217U
Test#1 (Integers)
2.56k
1.79k (x0.7)
Test#2 (FP)
6.54k
5.02k (x0.77)
Test#3 (Generic, ZIP)
2.76k
2.21k (x0.8)
Test#1 (Memory)
0.91k
2.31k (x2.54)
TOTAL
12.77k
11.32k (x0.89)

Multithread

E5500

i3-3217U
Test#1 (Integers)
4.32k
3.56k (x0.82)
Test#2 (FP)
10.8k
11.47k (x1.06)
Test#3 (Generic, ZIP)
4.7k
5.34k (x1.14)
Test#1 (Memory)
0.87k
2.54k (x2.91)
TOTAL
20.69k
22.91k (x1.11)

Performance/W
E5500
i3-3217U
Test#1 (Integers)
66 points/W
210 points/W
Test#2 (FP)
166 points/W
674 points/W
Test#3 (Generic, ZIP)
72 points/W
314 points/W
Test#1 (Memory)
13 points/W
149 points/W
TOTAL
318 points/W
1348 points/W

Performance/GHz
E5500
i3-3217U
Test#1 (Integers)
914 points/GHz
992 points/GHz
Test#2 (FP)
2335 points/GHz
2786 points/GHz
Test#3 (Generic, ZIP)
985 points/GHz
1227 points/GHz
Test#1 (Memory)
325 points/GHz
1283 points/GHz
TOTAL
4560 points/GHz
6288 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