| | | | | | |

Pentium G3260 vs Core i5-7300HQ


Description
The G3260 is based on Haswell architecture while the i5-7300HQ is based on Kaby Lake.

Using the multithread performance as a reference, the G3260 gets a score of 58.9 k points while the i5-7300HQ gets 130.4 k points.

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

Specs
CPUID
306c3
906e9
Core
Haswell
Kaby Lake-H
Architecture
Base frecuency
3.3 GHz
2.5 GHz
Boost frecuency
3.3 GHz
3.5 GHz
Socket
LGA1150
BGA1440
Cores/Threads
2/2
4/4
TDP
53 W
45 W
Cache L1 (d+i)
2x32+2x32 kB
4x32+4x32 kB
Cache L2
2x256 kB
4x256 kB
Cache L3
3072 kB
6144 kB
Date
March 2015
January 2017
Mean monothread perf.
30.56k points
53.51k points
Mean multithread perf.
58.89k points
168.81k 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
G3260
i5-7300HQ
Test#1 (Integers)
11.73k
11.71k (x1)
Test#2 (FP)
10.45k
16.74k (x1.6)
Test#3 (Generic, ZIP)
4.55k
4.27k (x0.94)
Test#1 (Memory)
3.83k
7.81k (x2.04)
TOTAL
30.56k
40.53k (x1.33)

Multithread

G3260

i5-7300HQ
Test#1 (Integers)
22.99k
44.38k (x1.93)
Test#2 (FP)
20.53k
62.55k (x3.05)
Test#3 (Generic, ZIP)
8.82k
15.6k (x1.77)
Test#1 (Memory)
6.55k
7.85k (x1.2)
TOTAL
58.89k
130.38k (x2.21)

Performance/W
G3260
i5-7300HQ
Test#1 (Integers)
434 points/W
986 points/W
Test#2 (FP)
387 points/W
1390 points/W
Test#3 (Generic, ZIP)
166 points/W
347 points/W
Test#1 (Memory)
124 points/W
174 points/W
TOTAL
1111 points/W
2897 points/W

Performance/GHz
G3260
i5-7300HQ
Test#1 (Integers)
3555 points/GHz
3347 points/GHz
Test#2 (FP)
3165 points/GHz
4783 points/GHz
Test#3 (Generic, ZIP)
1380 points/GHz
1221 points/GHz
Test#1 (Memory)
1161 points/GHz
2231 points/GHz
TOTAL
9261 points/GHz
11581 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