| | | | | | |

Athlon 3000G vs Core i7-6820HQ


Description
The 3000G is based on Zen+ architecture while the i7-6820HQ is based on Skylake.

Using the multithread performance as a reference, the 3000G gets a score of 95.8 k points while the i7-6820HQ gets 205.9 k points.

Summarizing, the i7-6820HQ is 2.1 times faster than the 3000G. To get a proper comparison between both models, take a look to the data shown below.

Specs
CPUID
810f81
506e3
Core
Picasso
Skylake-H
Architecture
Base frecuency
3.5 GHz
2.7 GHz
Boost frecuency
3.5 GHz
3.6 GHz
Socket
AM4
BGA1440
Cores/Threads
2/4
4/8
TDP
35 W
45 W
Cache L1 (d+i)
2x64+2x32 kB
4x32+4x32 kB
Cache L2
2x512 kB
4x256 kB
Cache L3
4096 kB
8192 kB
Date
November 2019
October 2015
Mean monothread perf.
43.82k points
50.1k points
Mean multithread perf.
95.84k points
205.89k 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
i7-6820HQ
Test#1 (Integers)
13.02k
20.99k (x1.61)
Test#2 (FP)
20.56k
18.63k (x0.91)
Test#3 (Generic, ZIP)
4.81k
4.33k (x0.9)
Test#1 (Memory)
5.43k
6.15k (x1.13)
TOTAL
43.82k
50.1k (x1.14)

Multithread

3000G

i7-6820HQ
Test#1 (Integers)
27.29k
91.8k (x3.36)
Test#2 (FP)
49.37k
87.24k (x1.77)
Test#3 (Generic, ZIP)
13.57k
20.55k (x1.51)
Test#1 (Memory)
5.61k
6.3k (x1.12)
TOTAL
95.84k
205.89k (x2.15)

Performance/W
3000G
i7-6820HQ
Test#1 (Integers)
780 points/W
2040 points/W
Test#2 (FP)
1411 points/W
1939 points/W
Test#3 (Generic, ZIP)
388 points/W
457 points/W
Test#1 (Memory)
160 points/W
140 points/W
TOTAL
2738 points/W
4575 points/W

Performance/GHz
3000G
i7-6820HQ
Test#1 (Integers)
3719 points/GHz
5831 points/GHz
Test#2 (FP)
5873 points/GHz
5174 points/GHz
Test#3 (Generic, ZIP)
1374 points/GHz
1204 points/GHz
Test#1 (Memory)
1553 points/GHz
1708 points/GHz
TOTAL
12519 points/GHz
13917 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