| | | | | | |

Core i5-3210M vs i3-9100T


Description
The i5-3210M is based on Ivy Bridge architecture while the i3-9100T 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 i3-9100T gets 147.9 k points.

Summarizing, the i3-9100T is 2.9 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
906eb
Core
Ivy Bridge
Coffee Lake-S
Architecture
Base frecuency
2.5 GHz
3.1 GHz
Boost frecuency
3.1 GHz
3.7 GHz
Socket
Socket G2 (988B)
LGA 1151
Cores/Threads
2 /2
4/4
TDP
35 W
35 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
June 2019
Mean monothread perf.
24.9k points
60.16k points
Mean multithread perf.
51.73k points
192.88k 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
i3-9100T
Test#1 (Integers)
3.08k
3.79k (x1.23)
Test#2 (FP)
8.58k
15.65k (x1.82)
Test#3 (Generic, ZIP)
3.76k
4.59k (x1.22)
Test#1 (Memory)
3.99k
7.78k (x1.95)
TOTAL
19.42k
31.81k (x1.64)

Multithread

i5-3210M

i3-9100T
Test#1 (Integers)
5.79k
13.97k (x2.41)
Test#2 (FP)
18.77k
57.83k (x3.08)
Test#3 (Generic, ZIP)
8.74k
17.03k (x1.95)
Test#1 (Memory)
4.59k
4.35k (x0.95)
TOTAL
37.89k
93.18k (x2.46)

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
i3-9100T
Test#1 (Integers)
8.59k
13.74k (x1.6)
Test#2 (FP)
8.88k
19.7k (x2.22)
Test#3 (Generic, ZIP)
3.59k
4.86k (x1.36)
Test#1 (Memory)
3.45k
8.61k (x2.49)
TOTAL
24.51k
46.91k (x1.91)

Multithread

i5-3210M

i3-9100T
Test#1 (Integers)
20.18k
50.5k (x2.5)
Test#2 (FP)
19.96k
72.58k (x3.64)
Test#3 (Generic, ZIP)
8.93k
18.09k (x2.02)
Test#1 (Memory)
4.6k
4.28k (x0.93)
TOTAL
53.67k
145.45k (x2.71)

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
i3-9100T
Test#1 (Integers)
9.11k
13.6k (x1.49)
Test#2 (FP)
8.88k
20.58k (x2.32)
Test#3 (Generic, ZIP)
3.46k
4.76k (x1.37)
Test#1 (Memory)
3.45k
8.8k (x2.55)
TOTAL
24.9k
47.74k (x1.92)

Multithread

i5-3210M

i3-9100T
Test#1 (Integers)
18.72k
50.18k (x2.68)
Test#2 (FP)
21.09k
75.99k (x3.6)
Test#3 (Generic, ZIP)
8.38k
17.66k (x2.11)
Test#1 (Memory)
3.54k
4.12k (x1.16)
TOTAL
51.73k
147.95k (x2.86)

Performance/W
i5-3210M
i3-9100T
Test#1 (Integers)
535 points/W
1434 points/W
Test#2 (FP)
603 points/W
2171 points/W
Test#3 (Generic, ZIP)
239 points/W
505 points/W
Test#1 (Memory)
101 points/W
118 points/W
TOTAL
1478 points/W
4227 points/W

Performance/GHz
i5-3210M
i3-9100T
Test#1 (Integers)
2939 points/GHz
3676 points/GHz
Test#2 (FP)
2863 points/GHz
5562 points/GHz
Test#3 (Generic, ZIP)
1117 points/GHz
1286 points/GHz
Test#1 (Memory)
1112 points/GHz
2378 points/GHz
TOTAL
8032 points/GHz
12902 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