| | | | | | |

Core i5-3210M vs i5-8500


Description
The i5-3210M is based on Ivy Bridge architecture while the i5-8500 is based on Coffee Lake.

Using the multithread performance as a reference, the i5-3210M gets a score of 51.7 k points while the i5-8500 gets 232.5 k points.

Summarizing, the i5-8500 is 4.5 times faster than the i5-3210M . 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
2.5 GHz
3 GHz
Boost frecuency
3.1 GHz
4.1 GHz
Socket
Socket G2 (988B)
LGA 1151
Cores/Threads
2 /2
6/6
TDP
35 W
65 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.
24.9k points
69.09k points
Mean multithread perf.
51.73k points
307.52k 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
i5-3210M
i5-8500
Test#1 (Integers)
3.08k
4.19k (x1.36)
Test#2 (FP)
8.58k
17.38k (x2.02)
Test#3 (Generic, ZIP)
3.76k
5.46k (x1.45)
Test#1 (Memory)
3.99k
11.92k (x2.99)
TOTAL
19.42k
38.96k (x2.01)

Multithread

i5-3210M

i5-8500
Test#1 (Integers)
5.79k
27.67k (x4.78)
Test#2 (FP)
18.77k
94.07k (x5.01)
Test#3 (Generic, ZIP)
8.74k
29.05k (x3.32)
Test#1 (Memory)
4.59k
4.39k (x0.96)
TOTAL
37.89k
155.18k (x4.1)

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
i5-3210M
i5-8500
Test#1 (Integers)
8.59k
15.22k (x1.77)
Test#2 (FP)
8.88k
22.02k (x2.48)
Test#3 (Generic, ZIP)
3.59k
5.75k (x1.6)
Test#1 (Memory)
3.45k
12.17k (x3.52)
TOTAL
24.51k
55.17k (x2.25)

Multithread

i5-3210M

i5-8500
Test#1 (Integers)
20.18k
87.78k (x4.35)
Test#2 (FP)
19.96k
126.73k (x6.35)
Test#3 (Generic, ZIP)
8.93k
32.93k (x3.69)
Test#1 (Memory)
4.6k
4.22k (x0.92)
TOTAL
53.67k
251.65k (x4.69)

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
i5-3210M
i5-8500
Test#1 (Integers)
9.11k
15.21k (x1.67)
Test#2 (FP)
8.88k
22.94k (x2.58)
Test#3 (Generic, ZIP)
3.46k
5.54k (x1.6)
Test#1 (Memory)
3.45k
11.39k (x3.3)
TOTAL
24.9k
55.07k (x2.21)

Multithread

i5-3210M

i5-8500
Test#1 (Integers)
18.72k
79.52k (x4.25)
Test#2 (FP)
21.09k
107.78k (x5.11)
Test#3 (Generic, ZIP)
8.38k
31.89k (x3.81)
Test#1 (Memory)
3.54k
13.37k (x3.77)
TOTAL
51.73k
232.55k (x4.5)

Performance/W
i5-3210M
i5-8500
Test#1 (Integers)
535 points/W
1223 points/W
Test#2 (FP)
603 points/W
1658 points/W
Test#3 (Generic, ZIP)
239 points/W
491 points/W
Test#1 (Memory)
101 points/W
206 points/W
TOTAL
1478 points/W
3578 points/W

Performance/GHz
i5-3210M
i5-8500
Test#1 (Integers)
2939 points/GHz
3709 points/GHz
Test#2 (FP)
2863 points/GHz
5595 points/GHz
Test#3 (Generic, ZIP)
1117 points/GHz
1351 points/GHz
Test#1 (Memory)
1112 points/GHz
2778 points/GHz
TOTAL
8032 points/GHz
13433 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