| | | | | | |

Core i3-3217U vs i3-10105


Description
The i3-3217U is based on Ivy Bridge architecture while the i3-10105 is based on Comet Lake.

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

Summarizing, the i3-10105 is 5.5 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
a0653
Core
Ivy Bridge
Comet Lake-S
Architecture
Base frecuency
1.8 GHz
3.7 GHz
Boost frecuency
1.8 GHz
4.4 GHz
Socket
BGA1023
LGA 1200
Cores/Threads
2 /2
4/8
TDP
17 W
65 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
March 2021
Mean monothread perf.
16.09k points
68.92k points
Mean multithread perf.
35.81k points
253.93k 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
i3-10105
Test#1 (Integers)
1.79k
4.5k (x2.52)
Test#2 (FP)
5.02k
18.39k (x3.67)
Test#3 (Generic, ZIP)
2.21k
5.78k (x2.62)
Test#1 (Memory)
2.31k
8.3k (x3.59)
TOTAL
11.32k
36.97k (x3.27)

Multithread

i3-3217U

i3-10105
Test#1 (Integers)
3.56k
16.13k (x4.53)
Test#2 (FP)
11.47k
75.62k (x6.59)
Test#3 (Generic, ZIP)
5.34k
27.88k (x5.22)
Test#1 (Memory)
2.54k
3.57k (x1.41)
TOTAL
22.91k
123.2k (x5.38)

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
i3-10105
Test#1 (Integers)
5.37k
16.19k (x3.01)
Test#2 (FP)
5.25k
23.07k (x4.39)
Test#3 (Generic, ZIP)
2.2k
6.04k (x2.74)
Test#1 (Memory)
2.25k
8.46k (x3.76)
TOTAL
15.08k
53.77k (x3.57)

Multithread

i3-3217U

i3-10105
Test#1 (Integers)
12.46k
57.59k (x4.62)
Test#2 (FP)
12.14k
100.63k (x8.29)
Test#3 (Generic, ZIP)
5.52k
28.59k (x5.18)
Test#1 (Memory)
2.64k
3.56k (x1.35)
TOTAL
32.75k
190.38k (x5.81)

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
i3-10105
Test#1 (Integers)
5.83k
16.11k (x2.76)
Test#2 (FP)
5.79k
24.12k (x4.17)
Test#3 (Generic, ZIP)
2.22k
5.71k (x2.58)
Test#1 (Memory)
2.26k
7.89k (x3.49)
TOTAL
16.09k
53.83k (x3.34)

Multithread

i3-3217U

i3-10105
Test#1 (Integers)
12.53k
58.25k (x4.65)
Test#2 (FP)
14.19k
105.73k (x7.45)
Test#3 (Generic, ZIP)
5.63k
27.8k (x4.93)
Test#1 (Memory)
3.46k
3.51k (x1.01)
TOTAL
35.81k
195.29k (x5.45)

Performance/W
i3-3217U
i3-10105
Test#1 (Integers)
737 points/W
896 points/W
Test#2 (FP)
835 points/W
1627 points/W
Test#3 (Generic, ZIP)
331 points/W
428 points/W
Test#1 (Memory)
204 points/W
54 points/W
TOTAL
2107 points/W
3004 points/W

Performance/GHz
i3-3217U
i3-10105
Test#1 (Integers)
3238 points/GHz
3662 points/GHz
Test#2 (FP)
3217 points/GHz
5481 points/GHz
Test#3 (Generic, ZIP)
1232 points/GHz
1298 points/GHz
Test#1 (Memory)
1255 points/GHz
1793 points/GHz
TOTAL
8942 points/GHz
12235 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