| | | | | | |

Core i5-3317U vs i3-10100T


Description
The i5-3317U is based on Ivy Bridge architecture while the i3-10100T is based on Comet Lake.

Using the multithread performance as a reference, the i5-3317U gets a score of 41.3 k points while the i3-10100T gets 175.2 k points.

Summarizing, the i3-10100T is 4.2 times faster than the i5-3317U . 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.7 GHz
3.6 GHz
Boost frecuency
2.6 GHz
4.3 GHz
Socket
BGA1023
FC-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
April 2020
Mean monothread perf.
17.88k points
60.06k points
Mean multithread perf.
41.31k points
227.67k 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-3317U
i3-10100T
Test#1 (Integers)
2.5k
4.32k (x1.73)
Test#2 (FP)
7.18k
15.7k (x2.19)
Test#3 (Generic, ZIP)
3.19k
5.04k (x1.58)
Test#1 (Memory)
3.41k
7.68k (x2.25)
TOTAL
16.27k
32.73k (x2.01)

Multithread

i5-3317U

i3-10100T
Test#1 (Integers)
4.93k
16.59k (x3.36)
Test#2 (FP)
15.72k
71.1k (x4.52)
Test#3 (Generic, ZIP)
7.53k
23.26k (x3.09)
Test#1 (Memory)
4.21k
3.86k (x0.92)
TOTAL
32.39k
114.81k (x3.54)

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-3317U
i3-10100T
Test#1 (Integers)
8.38k
13.84k (x1.65)
Test#2 (FP)
7.76k
19.79k (x2.55)
Test#3 (Generic, ZIP)
3.33k
5.28k (x1.59)
Test#1 (Memory)
3.41k
8.31k (x2.44)
TOTAL
22.88k
47.22k (x2.06)

Multithread

i5-3317U

i3-10100T
Test#1 (Integers)
16.56k
54.67k (x3.3)
Test#2 (FP)
16.79k
90.71k (x5.4)
Test#3 (Generic, ZIP)
7.85k
24.11k (x3.07)
Test#1 (Memory)
4.02k
3.85k (x0.96)
TOTAL
45.23k
173.34k (x3.83)

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-3317U
i3-10100T
Test#1 (Integers)
6.11k
13.88k (x2.27)
Test#2 (FP)
6.58k
20.94k (x3.18)
Test#3 (Generic, ZIP)
2.48k
5.18k (x2.09)
Test#1 (Memory)
2.71k
8.2k (x3.02)
TOTAL
17.88k
48.19k (x2.69)

Multithread

i5-3317U

i3-10100T
Test#1 (Integers)
13.67k
54.88k (x4.01)
Test#2 (FP)
16.8k
93.17k (x5.55)
Test#3 (Generic, ZIP)
6.66k
23.34k (x3.5)
Test#1 (Memory)
4.17k
3.85k (x0.92)
TOTAL
41.31k
175.24k (x4.24)

Performance/W
i5-3317U
i3-10100T
Test#1 (Integers)
804 points/W
844 points/W
Test#2 (FP)
988 points/W
1433 points/W
Test#3 (Generic, ZIP)
392 points/W
359 points/W
Test#1 (Memory)
246 points/W
59 points/W
TOTAL
2430 points/W
2696 points/W

Performance/GHz
i5-3317U
i3-10100T
Test#1 (Integers)
2351 points/GHz
3228 points/GHz
Test#2 (FP)
2532 points/GHz
4869 points/GHz
Test#3 (Generic, ZIP)
953 points/GHz
1204 points/GHz
Test#1 (Memory)
1043 points/GHz
1907 points/GHz
TOTAL
6879 points/GHz
11208 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