| | | | | | |

Core i5-8250U vs i5-3210M


Description
The i5-8250U is based on Kaby Lake architecture while the i5-3210M is based on Ivy Bridge.

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

Summarizing, the i5-8250U is 2.7 times faster than the i5-3210M . To get a proper comparison between both models, take a look to the data shown below.

Specs
CPUID
806ea
306a9
Core
Kaby Lake-R
Ivy Bridge
Architecture
Base frecuency
1.6 GHz
2.5 GHz
Boost frecuency
3.4 GHz
3.1 GHz
Socket
BGA1356
Socket G2 (988B)
Cores/Threads
4/8
2 /2
TDP
15 W
35 W
Cache L1 (d+i)
4x32+4x32 kB
2x32+2x32 kB
Cache L2
4x256 kB
2x256 kB
Cache L3
6144 kB
3072 kB
Date
August 2017
June 2012
Mean monothread perf.
54.31k points
24.9k points
Mean multithread perf.
161.26k points
51.73k 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-8250U
i5-3210M
Test#1 (Integers)
3.32k
3.08k (x0.93)
Test#2 (FP)
13.5k
8.58k (x0.64)
Test#3 (Generic, ZIP)
4.11k
3.76k (x0.92)
Test#1 (Memory)
7.42k
3.99k (x0.54)
TOTAL
28.34k
19.42k (x0.69)

Multithread

i5-8250U

i5-3210M
Test#1 (Integers)
13.97k
5.79k (x0.41)
Test#2 (FP)
50.8k
18.77k (x0.37)
Test#3 (Generic, ZIP)
14.71k
8.74k (x0.59)
Test#1 (Memory)
4.76k
4.59k (x0.96)
TOTAL
84.24k
37.89k (x0.45)

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-8250U
i5-3210M
Test#1 (Integers)
12.41k
8.59k (x0.69)
Test#2 (FP)
18.11k
8.88k (x0.49)
Test#3 (Generic, ZIP)
4.79k
3.59k (x0.75)
Test#1 (Memory)
8.16k
3.45k (x0.42)
TOTAL
43.46k
24.51k (x0.56)

Multithread

i5-8250U

i5-3210M
Test#1 (Integers)
42.48k
20.18k (x0.48)
Test#2 (FP)
60.2k
19.96k (x0.33)
Test#3 (Generic, ZIP)
14.85k
8.93k (x0.6)
Test#1 (Memory)
4.77k
4.6k (x0.96)
TOTAL
122.3k
53.67k (x0.44)

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-8250U
i5-3210M
Test#1 (Integers)
12.59k
9.11k (x0.72)
Test#2 (FP)
18.89k
8.88k (x0.47)
Test#3 (Generic, ZIP)
4.65k
3.46k (x0.74)
Test#1 (Memory)
8.2k
3.45k (x0.42)
TOTAL
44.32k
24.9k (x0.56)

Multithread

i5-8250U

i5-3210M
Test#1 (Integers)
45.91k
18.72k (x0.41)
Test#2 (FP)
69.55k
21.09k (x0.3)
Test#3 (Generic, ZIP)
16.79k
8.38k (x0.5)
Test#1 (Memory)
4.83k
3.54k (x0.73)
TOTAL
137.09k
51.73k (x0.38)

Performance/W
i5-8250U
i5-3210M
Test#1 (Integers)
3061 points/W
535 points/W
Test#2 (FP)
4637 points/W
603 points/W
Test#3 (Generic, ZIP)
1120 points/W
239 points/W
Test#1 (Memory)
322 points/W
101 points/W
TOTAL
9139 points/W
1478 points/W

Performance/GHz
i5-8250U
i5-3210M
Test#1 (Integers)
3702 points/GHz
2939 points/GHz
Test#2 (FP)
5556 points/GHz
2863 points/GHz
Test#3 (Generic, ZIP)
1367 points/GHz
1117 points/GHz
Test#1 (Memory)
2411 points/GHz
1112 points/GHz
TOTAL
13036 points/GHz
8032 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