| | | | | | |

Core i3-3217U vs Xeon E5-2620 v4


Description
The i3-3217U is based on Ivy Bridge architecture while the E5-2620 v4 is based on Broadwell.

Using the multithread performance as a reference, the i3-3217U gets a score of 35.8 k points while the E5-2620 v4 gets 147.8 k points.

Summarizing, the E5-2620 v4 is 4.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
306a9
406f1
Core
Ivy Bridge
Broadwell-EP
Architecture
Base frecuency
1.8 GHz
2.1 GHz
Boost frecuency
1.8 GHz
3 GHz
Socket
BGA1023
Socket 2011-3
Cores/Threads
2 /2
8/16
TDP
17 W
85 W
Cache L1 (d+i)
2x32+2x32 kB
8x32+8x32 kB
Cache L2
2x256 kB
8x256 kB
Cache L3
3072 kB
20480 kB
Date
June 2012
March 2016
Mean monothread perf.
16.09k points
29.39k points
Mean multithread perf.
35.81k points
237.83k 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
i3-3217U
E5-2620 v4
Test#1 (Integers)
1.79k
2.6k (x1.46)
Test#2 (FP)
5.02k
7.55k (x1.51)
Test#3 (Generic, ZIP)
2.21k
2.61k (x1.18)
Test#1 (Memory)
2.31k
2.03k (x0.88)
TOTAL
11.32k
14.79k (x1.31)

Multithread

i3-3217U

E5-2620 v4
Test#1 (Integers)
3.56k
17.41k (x4.89)
Test#2 (FP)
11.47k
75.46k (x6.58)
Test#3 (Generic, ZIP)
5.34k
26.25k (x4.92)
Test#1 (Memory)
2.54k
4.65k (x1.83)
TOTAL
22.91k
123.78k (x5.4)

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
E5-2620 v4
Test#1 (Integers)
5.37k
8.22k (x1.53)
Test#2 (FP)
5.25k
12.06k (x2.3)
Test#3 (Generic, ZIP)
2.2k
4.01k (x1.82)
Test#1 (Memory)
2.25k
2.89k (x1.28)
TOTAL
15.08k
27.18k (x1.8)

Multithread

i3-3217U

E5-2620 v4
Test#1 (Integers)
12.46k
61.34k (x4.92)
Test#2 (FP)
12.14k
90.21k (x7.43)
Test#3 (Generic, ZIP)
5.52k
26.2k (x4.75)
Test#1 (Memory)
2.64k
4.62k (x1.75)
TOTAL
32.75k
182.37k (x5.57)

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
i3-3217U
E5-2620 v4
Test#1 (Integers)
5.83k
6.04k (x1.04)
Test#2 (FP)
5.79k
10.18k (x1.76)
Test#3 (Generic, ZIP)
2.22k
2.74k (x1.24)
Test#1 (Memory)
2.26k
2.41k (x1.06)
TOTAL
16.09k
21.37k (x1.33)

Multithread

i3-3217U

E5-2620 v4
Test#1 (Integers)
12.53k
47.51k (x3.79)
Test#2 (FP)
14.19k
75.12k (x5.29)
Test#3 (Generic, ZIP)
5.63k
19.72k (x3.5)
Test#1 (Memory)
3.46k
5.45k (x1.58)
TOTAL
35.81k
147.8k (x4.13)

Performance/W
i3-3217U
E5-2620 v4
Test#1 (Integers)
737 points/W
559 points/W
Test#2 (FP)
835 points/W
884 points/W
Test#3 (Generic, ZIP)
331 points/W
232 points/W
Test#1 (Memory)
204 points/W
64 points/W
TOTAL
2107 points/W
1739 points/W

Performance/GHz
i3-3217U
E5-2620 v4
Test#1 (Integers)
3238 points/GHz
2013 points/GHz
Test#2 (FP)
3217 points/GHz
3393 points/GHz
Test#3 (Generic, ZIP)
1232 points/GHz
915 points/GHz
Test#1 (Memory)
1255 points/GHz
802 points/GHz
TOTAL
8942 points/GHz
7123 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