| | | | | | |

Core i3-3217U vs i5-8265U


Description
The i3-3217U is based on Ivy Bridge architecture while the i5-8265U is based on Whiskey Lake.

Using the multithread performance as a reference, the i3-3217U gets a score of 35.8 k points while the i5-8265U gets 151.4 k points.

Summarizing, the i5-8265U is 4.2 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
806ec
Core
Ivy Bridge
Whiskey Lake-U
Architecture
Base frecuency
1.8 GHz
1.6 GHz
Boost frecuency
1.8 GHz
3.9 GHz
Socket
BGA1023
BGA1528
Cores/Threads
2 /2
4/8
TDP
17 W
15 W
Cache L1 (d+i)
2x32+2x32 kB
4x32+4x32 kB
Cache L2
2x256 kB
4x256 kB
Cache L3
3072 kB
6144 kB
Date
June 2012
August 2018
Mean monothread perf.
16.09k points
46.67k points
Mean multithread perf.
35.81k points
143.23k 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
i5-8265U
Test#1 (Integers)
1.79k
3.68k (x2.06)
Test#2 (FP)
5.02k
16.08k (x3.21)
Test#3 (Generic, ZIP)
2.21k
4.99k (x2.26)
Test#1 (Memory)
2.31k
7.95k (x3.44)
TOTAL
11.32k
32.69k (x2.89)

Multithread

i3-3217U

i5-8265U
Test#1 (Integers)
3.56k
14.29k (x4.01)
Test#2 (FP)
11.47k
61.15k (x5.33)
Test#3 (Generic, ZIP)
5.34k
16.53k (x3.1)
Test#1 (Memory)
2.54k
3.72k (x1.47)
TOTAL
22.91k
95.69k (x4.18)

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-8265U
Test#1 (Integers)
5.37k
13.6k (x2.53)
Test#2 (FP)
5.25k
20.03k (x3.81)
Test#3 (Generic, ZIP)
2.2k
5.19k (x2.36)
Test#1 (Memory)
2.25k
7.05k (x3.14)
TOTAL
15.08k
45.87k (x3.04)

Multithread

i3-3217U

i5-8265U
Test#1 (Integers)
12.46k
51.42k (x4.13)
Test#2 (FP)
12.14k
77.48k (x6.38)
Test#3 (Generic, ZIP)
5.52k
16.65k (x3.02)
Test#1 (Memory)
2.64k
3.69k (x1.4)
TOTAL
32.75k
149.24k (x4.56)

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
i5-8265U
Test#1 (Integers)
5.83k
13.66k (x2.34)
Test#2 (FP)
5.79k
21.17k (x3.66)
Test#3 (Generic, ZIP)
2.22k
5k (x2.26)
Test#1 (Memory)
2.26k
8.11k (x3.59)
TOTAL
16.09k
47.94k (x2.98)

Multithread

i3-3217U

i5-8265U
Test#1 (Integers)
12.53k
51.36k (x4.1)
Test#2 (FP)
14.19k
79.72k (x5.62)
Test#3 (Generic, ZIP)
5.63k
16.61k (x2.95)
Test#1 (Memory)
3.46k
3.75k (x1.08)
TOTAL
35.81k
151.44k (x4.23)

Performance/W
i3-3217U
i5-8265U
Test#1 (Integers)
737 points/W
3424 points/W
Test#2 (FP)
835 points/W
5314 points/W
Test#3 (Generic, ZIP)
331 points/W
1108 points/W
Test#1 (Memory)
204 points/W
250 points/W
TOTAL
2107 points/W
10096 points/W

Performance/GHz
i3-3217U
i5-8265U
Test#1 (Integers)
3238 points/GHz
3502 points/GHz
Test#2 (FP)
3217 points/GHz
5429 points/GHz
Test#3 (Generic, ZIP)
1232 points/GHz
1282 points/GHz
Test#1 (Memory)
1255 points/GHz
2081 points/GHz
TOTAL
8942 points/GHz
12293 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