| | | | | | |

Core i7-6820HQ vs Pentium G3260


Description
The i7-6820HQ is based on Skylake architecture while the G3260 is based on Haswell.

Using the multithread performance as a reference, the i7-6820HQ gets a score of 152.1 k points while the G3260 gets 58.9 k points.

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

Specs
CPUID
506e3
306c3
Core
Skylake-H
Haswell
Architecture
Base frecuency
2.7 GHz
3.3 GHz
Boost frecuency
3.6 GHz
3.3 GHz
Socket
BGA1440
LGA1150
Cores/Threads
4/8
2/2
TDP
45 W
53 W
Cache L1 (d+i)
4x32+4x32 kB
2x32+2x32 kB
Cache L2
4x256 kB
2x256 kB
Cache L3
8192 kB
3072 kB
Date
October 2015
March 2015
Mean monothread perf.
50.1k points
30.56k points
Mean multithread perf.
205.89k points
58.89k points

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
i7-6820HQ
G3260
Test#1 (Integers)
11.54k
11.73k (x1.02)
Test#2 (FP)
16.69k
10.45k (x0.63)
Test#3 (Generic, ZIP)
4.51k
4.55k (x1.01)
Test#1 (Memory)
7.27k
3.83k (x0.53)
TOTAL
40.01k
30.56k (x0.76)

Multithread

i7-6820HQ

G3260
Test#1 (Integers)
48.5k
22.99k (x0.47)
Test#2 (FP)
77.02k
20.53k (x0.27)
Test#3 (Generic, ZIP)
21.3k
8.82k (x0.41)
Test#1 (Memory)
5.24k
6.55k (x1.25)
TOTAL
152.06k
58.89k (x0.39)

Performance/W
i7-6820HQ
G3260
Test#1 (Integers)
1078 points/W
434 points/W
Test#2 (FP)
1711 points/W
387 points/W
Test#3 (Generic, ZIP)
473 points/W
166 points/W
Test#1 (Memory)
116 points/W
124 points/W
TOTAL
3379 points/W
1111 points/W

Performance/GHz
i7-6820HQ
G3260
Test#1 (Integers)
3205 points/GHz
3555 points/GHz
Test#2 (FP)
4635 points/GHz
3165 points/GHz
Test#3 (Generic, ZIP)
1254 points/GHz
1380 points/GHz
Test#1 (Memory)
2020 points/GHz
1161 points/GHz
TOTAL
11114 points/GHz
9261 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