| | | | | | |

Core i3-3217U vs i5-8500T


Description
The i3-3217U is based on Ivy Bridge architecture while the i5-8500T is based on Coffee Lake.

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

Summarizing, the i5-8500T is 5.3 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
906ea
Core
Ivy Bridge
Coffee Lake-S
Architecture
Base frecuency
1.8 GHz
2.1 GHz
Boost frecuency
1.8 GHz
3.5 GHz
Socket
BGA1023
LGA 1151
Cores/Threads
2 /2
6/6
TDP
17 W
35 W
Cache L1 (d+i)
2x32+2x32 kB
6x32+6x32 kB
Cache L2
2x256 kB
6x256 kB
Cache L3
3072 kB
9216 kB
Date
June 2012
March 2018
Mean monothread perf.
16.09k points
59.27k points
Mean multithread perf.
35.81k points
251.82k 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-8500T
Test#1 (Integers)
1.79k
3.56k (x1.99)
Test#2 (FP)
5.02k
14.76k (x2.94)
Test#3 (Generic, ZIP)
2.21k
4.46k (x2.02)
Test#1 (Memory)
2.31k
8.72k (x3.78)
TOTAL
11.32k
31.5k (x2.78)

Multithread

i3-3217U

i5-8500T
Test#1 (Integers)
3.56k
19.37k (x5.44)
Test#2 (FP)
11.47k
82.35k (x7.18)
Test#3 (Generic, ZIP)
5.34k
24.6k (x4.61)
Test#1 (Memory)
2.54k
2.97k (x1.17)
TOTAL
22.91k
129.29k (x5.64)

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-8500T
Test#1 (Integers)
5.37k
12.93k (x2.41)
Test#2 (FP)
5.25k
18.61k (x3.54)
Test#3 (Generic, ZIP)
2.2k
4.76k (x2.16)
Test#1 (Memory)
2.25k
10.05k (x4.47)
TOTAL
15.08k
46.36k (x3.07)

Multithread

i3-3217U

i5-8500T
Test#1 (Integers)
12.46k
71.15k (x5.71)
Test#2 (FP)
12.14k
102.74k (x8.46)
Test#3 (Generic, ZIP)
5.52k
26.6k (x4.82)
Test#1 (Memory)
2.64k
2.9k (x1.1)
TOTAL
32.75k
203.39k (x6.21)

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-8500T
Test#1 (Integers)
5.83k
12.92k (x2.22)
Test#2 (FP)
5.79k
19.47k (x3.36)
Test#3 (Generic, ZIP)
2.22k
4.62k (x2.08)
Test#1 (Memory)
2.26k
9.6k (x4.25)
TOTAL
16.09k
46.6k (x2.9)

Multithread

i3-3217U

i5-8500T
Test#1 (Integers)
12.53k
71.25k (x5.69)
Test#2 (FP)
14.19k
91.16k (x6.42)
Test#3 (Generic, ZIP)
5.63k
24.45k (x4.34)
Test#1 (Memory)
3.46k
2.85k (x0.82)
TOTAL
35.81k
189.71k (x5.3)

Performance/W
i3-3217U
i5-8500T
Test#1 (Integers)
737 points/W
2036 points/W
Test#2 (FP)
835 points/W
2604 points/W
Test#3 (Generic, ZIP)
331 points/W
699 points/W
Test#1 (Memory)
204 points/W
81 points/W
TOTAL
2107 points/W
5420 points/W

Performance/GHz
i3-3217U
i5-8500T
Test#1 (Integers)
3238 points/GHz
3691 points/GHz
Test#2 (FP)
3217 points/GHz
5562 points/GHz
Test#3 (Generic, ZIP)
1232 points/GHz
1320 points/GHz
Test#1 (Memory)
1255 points/GHz
2742 points/GHz
TOTAL
8942 points/GHz
13315 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