| | | | | | |

Ryzen 3 2200U vs Core i3-6100T


Description
The 2200U is based on Zen architecture while the i3-6100T is based on Skylake.

Using the multithread performance as a reference, the 2200U gets a score of 71 k points while the i3-6100T gets 105.2 k points.

Summarizing, the i3-6100T is 1.5 times faster than the 2200U. To get a proper comparison between both models, take a look to the data shown below.

Specs
CPUID
810f10
506e3
Core
Raven Ridge
Skylake-S
Architecture
Base frecuency
2.5 GHz
3.2 GHz
Boost frecuency
3.4 GHz
3.2 GHz
Socket
BGA-FP5
LGA 1151
Cores/Threads
2/4
2/4
TDP
15 W
35 W
Cache L1 (d+i)
2x64+2x32 kB
2x32+2x32 kB
Cache L2
2x512 kB
2x256 kB
Cache L3
4096 kB
3072 kB
Date
January 2018
November 2015
Mean monothread perf.
36.77k points
43.92k points
Mean multithread perf.
71.02k points
105.21k 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
2200U
i3-6100T
Test#1 (Integers)
2.63k
3.14k (x1.19)
Test#2 (FP)
7.84k
12.26k (x1.56)
Test#3 (Generic, ZIP)
3.63k
3.94k (x1.09)
Test#1 (Memory)
2.93k
2.21k (x0.75)
TOTAL
17.02k
21.55k (x1.27)

Multithread

2200U

i3-6100T
Test#1 (Integers)
5.77k
6.52k (x1.13)
Test#2 (FP)
24.15k
30.61k (x1.27)
Test#3 (Generic, ZIP)
9.28k
10.59k (x1.14)
Test#1 (Memory)
2.83k
2.77k (x0.98)
TOTAL
42.02k
50.49k (x1.2)

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
2200U
i3-6100T
Test#1 (Integers)
11.54k
10.46k (x0.91)
Test#2 (FP)
19.69k
17.55k (x0.89)
Test#3 (Generic, ZIP)
4.55k
3.71k (x0.82)
Test#1 (Memory)
3.25k
3.07k (x0.94)
TOTAL
39.03k
34.79k (x0.89)

Multithread

2200U

i3-6100T
Test#1 (Integers)
19.25k
23.92k (x1.24)
Test#2 (FP)
36.27k
42.11k (x1.16)
Test#3 (Generic, ZIP)
10.2k
10.51k (x1.03)
Test#1 (Memory)
3.07k
2.57k (x0.84)
TOTAL
68.8k
79.1k (x1.15)

AVX2 optimized benchmark
The benchmark in mode III (AVX2), like AVX1, is optimized to used 256 bits registers beside the second version of the Advanced Vector Extensions (AVX). The first AVX2 compatible CPU was released in 2013.
Monothread
2200U
i3-6100T
Test#1 (Integers)
10.73k
19.58k (x1.82)
Test#2 (FP)
18.15k
16.97k (x0.93)
Test#3 (Generic, ZIP)
3.99k
3.91k (x0.98)
Test#1 (Memory)
3.89k
3.47k (x0.89)
TOTAL
36.77k
43.92k (x1.19)

Multithread

2200U

i3-6100T
Test#1 (Integers)
20.11k
47.02k (x2.34)
Test#2 (FP)
36.87k
44.41k (x1.2)
Test#3 (Generic, ZIP)
10.74k
9.93k (x0.92)
Test#1 (Memory)
3.31k
3.85k (x1.17)
TOTAL
71.02k
105.21k (x1.48)

Performance/W
2200U
i3-6100T
Test#1 (Integers)
1340 points/W
1344 points/W
Test#2 (FP)
2458 points/W
1269 points/W
Test#3 (Generic, ZIP)
716 points/W
284 points/W
Test#1 (Memory)
220 points/W
110 points/W
TOTAL
4735 points/W
3006 points/W

Performance/GHz
2200U
i3-6100T
Test#1 (Integers)
3157 points/GHz
6119 points/GHz
Test#2 (FP)
5338 points/GHz
5303 points/GHz
Test#3 (Generic, ZIP)
1175 points/GHz
1221 points/GHz
Test#1 (Memory)
1144 points/GHz
1084 points/GHz
TOTAL
10814 points/GHz
13726 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