| | | | | | |

Pentium G3260 vs Core i5-1135G7


Description
The G3260 is based on Haswell architecture while the i5-1135G7 is based on Tiger Lake.

Using the multithread performance as a reference, the G3260 gets a score of 58.9 k points while the i5-1135G7 gets 141.4 k points.

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

Specs
CPUID
306c3
806c1
Core
Haswell
Tiger Lake UP3
Architecture
Base frecuency
3.3 GHz
2.4 GHz
Boost frecuency
3.3 GHz
4.2 GHz
Socket
LGA1150
BGA 1449
Cores/Threads
2/2
4/8
TDP
53 W
28 W
Cache L1 (d+i)
2x32+2x32 kB
4x32+4x48 kB
Cache L2
2x256 kB
4x1280 kB
Cache L3
3072 kB
8192 kB
Date
March 2015
September 2020
Mean monothread perf.
30.56k points
68.19k points
Mean multithread perf.
58.89k points
238.87k 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-1135G7
Test#1 (Integers)
11.73k
13.43k (x1.14)
Test#2 (FP)
10.45k
22.29k (x2.13)
Test#3 (Generic, ZIP)
4.55k
11.18k (x2.45)
Test#1 (Memory)
3.83k
9.75k (x2.55)
TOTAL
30.56k
56.64k (x1.85)

Multithread

G3260

i5-1135G7
Test#1 (Integers)
22.99k
40.24k (x1.75)
Test#2 (FP)
20.53k
65.99k (x3.21)
Test#3 (Generic, ZIP)
8.82k
28.51k (x3.23)
Test#1 (Memory)
6.55k
6.66k (x1.02)
TOTAL
58.89k
141.4k (x2.4)

Performance/W
G3260
i5-1135G7
Test#1 (Integers)
434 points/W
1437 points/W
Test#2 (FP)
387 points/W
2357 points/W
Test#3 (Generic, ZIP)
166 points/W
1018 points/W
Test#1 (Memory)
124 points/W
238 points/W
TOTAL
1111 points/W
5050 points/W

Performance/GHz
G3260
i5-1135G7
Test#1 (Integers)
3555 points/GHz
3197 points/GHz
Test#2 (FP)
3165 points/GHz
5306 points/GHz
Test#3 (Generic, ZIP)
1380 points/GHz
2661 points/GHz
Test#1 (Memory)
1161 points/GHz
2321 points/GHz
TOTAL
9261 points/GHz
13486 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