| | | | | | |

Athlon 3000G vs Core i5-8265U


Description
The 3000G is based on Zen+ architecture while the i5-8265U is based on Whiskey Lake.

Using the multithread performance as a reference, the 3000G gets a score of 95.8 k points while the i5-8265U gets 149.5 k points.

Summarizing, the i5-8265U is 1.6 times faster than the 3000G. To get a proper comparison between both models, take a look to the data shown below.

Specs
CPUID
810f81
806eb
Core
Picasso
Whiskey Lake-U
Architecture
Base frecuency
3.5 GHz
1.6 GHz
Boost frecuency
3.5 GHz
3.9 GHz
Socket
AM4
BGA 1528
Cores/Threads
2/4
4/8
TDP
35 W
15 W
Cache L1 (d+i)
2x64+2x32 kB
4x32+4x32 kB
Cache L2
2x512 kB
4x256 kB
Cache L3
4096 kB
6144 kB
Date
November 2019
August 2018
Mean monothread perf.
43.82k points
57.57k points
Mean multithread perf.
95.84k points
149.48k points

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
3000G
i5-8265U
Test#1 (Integers)
13.02k
24.32k (x1.87)
Test#2 (FP)
20.56k
20.35k (x0.99)
Test#3 (Generic, ZIP)
4.81k
4.38k (x0.91)
Test#1 (Memory)
5.43k
8.52k (x1.57)
TOTAL
43.82k
57.57k (x1.31)

Multithread

3000G

i5-8265U
Test#1 (Integers)
27.29k
65.17k (x2.39)
Test#2 (FP)
49.37k
63.6k (x1.29)
Test#3 (Generic, ZIP)
13.57k
14.4k (x1.06)
Test#1 (Memory)
5.61k
6.31k (x1.12)
TOTAL
95.84k
149.48k (x1.56)

Performance/W
3000G
i5-8265U
Test#1 (Integers)
780 points/W
4345 points/W
Test#2 (FP)
1411 points/W
4240 points/W
Test#3 (Generic, ZIP)
388 points/W
960 points/W
Test#1 (Memory)
160 points/W
421 points/W
TOTAL
2738 points/W
9965 points/W

Performance/GHz
3000G
i5-8265U
Test#1 (Integers)
3719 points/GHz
6235 points/GHz
Test#2 (FP)
5873 points/GHz
5219 points/GHz
Test#3 (Generic, ZIP)
1374 points/GHz
1124 points/GHz
Test#1 (Memory)
1553 points/GHz
2183 points/GHz
TOTAL
12519 points/GHz
14762 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