| | | | | | |

Core i5-3210M vs i5-1135G7


Description
The i5-3210M is based on Ivy Bridge architecture while the i5-1135G7 is based on Tiger Lake.

Using the multithread performance as a reference, the i5-3210M gets a score of 51.7 k points while the i5-1135G7 gets 157.1 k points.

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

Specs
CPUID
306a9
806c1
Core
Ivy Bridge
Tiger Lake UP3
Architecture
Base frecuency
2.5 GHz
2.4 GHz
Boost frecuency
3.1 GHz
4.2 GHz
Socket
Socket G2 (988B)
BGA 1449
Cores/Threads
2 /2
4/8
TDP
35 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
June 2012
September 2020
Mean monothread perf.
24.9k points
68.08k points
Mean multithread perf.
51.73k points
237.55k points

Non-optimized benchmark
The benchmark in Mode 0 (FPU) measures cpu performance with non-optimized software. It uses the basic µinstructions from the i386 architecture with the i387 floating point unit. This mode is compatible with all CPUs so it's practical to compare very different CPUs
Monothread
i5-3210M
i5-1135G7
Test#1 (Integers)
3.08k
3.75k (x1.22)
Test#2 (FP)
8.58k
17.28k (x2.01)
Test#3 (Generic, ZIP)
3.76k
9.5k (x2.52)
Test#1 (Memory)
3.99k
8.81k (x2.21)
TOTAL
19.42k
39.34k (x2.03)

Multithread

i5-3210M

i5-1135G7
Test#1 (Integers)
5.79k
12.43k (x2.15)
Test#2 (FP)
18.77k
54.95k (x2.93)
Test#3 (Generic, ZIP)
8.74k
26.41k (x3.02)
Test#1 (Memory)
4.59k
7.38k (x1.61)
TOTAL
37.89k
101.16k (x2.67)

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
i5-3210M
i5-1135G7
Test#1 (Integers)
8.59k
13.43k (x1.56)
Test#2 (FP)
8.88k
22.29k (x2.51)
Test#3 (Generic, ZIP)
3.59k
11.18k (x3.12)
Test#1 (Memory)
3.45k
9.75k (x2.82)
TOTAL
24.51k
56.64k (x2.31)

Multithread

i5-3210M

i5-1135G7
Test#1 (Integers)
20.18k
40.24k (x1.99)
Test#2 (FP)
19.96k
65.99k (x3.31)
Test#3 (Generic, ZIP)
8.93k
28.51k (x3.19)
Test#1 (Memory)
4.6k
6.66k (x1.45)
TOTAL
53.67k
141.4k (x2.63)

AVX optimized benchmark
The benchmark in mode II (AVX) is optimized to used 256 bits registers beside the first version of the Advanced Vector Extensions (AVX). The first AVX compatible CPU was released in 2011.
Monothread
i5-3210M
i5-1135G7
Test#1 (Integers)
9.11k
15.12k (x1.66)
Test#2 (FP)
8.88k
23.4k (x2.64)
Test#3 (Generic, ZIP)
3.46k
10.9k (x3.15)
Test#1 (Memory)
3.45k
9.41k (x2.73)
TOTAL
24.9k
58.83k (x2.36)

Multithread

i5-3210M

i5-1135G7
Test#1 (Integers)
18.72k
45.69k (x2.44)
Test#2 (FP)
21.09k
74.42k (x3.53)
Test#3 (Generic, ZIP)
8.38k
29.8k (x3.56)
Test#1 (Memory)
3.54k
7.16k (x2.02)
TOTAL
51.73k
157.08k (x3.04)

Performance/W
i5-3210M
i5-1135G7
Test#1 (Integers)
535 points/W
1632 points/W
Test#2 (FP)
603 points/W
2658 points/W
Test#3 (Generic, ZIP)
239 points/W
1064 points/W
Test#1 (Memory)
101 points/W
256 points/W
TOTAL
1478 points/W
5610 points/W

Performance/GHz
i5-3210M
i5-1135G7
Test#1 (Integers)
2939 points/GHz
3600 points/GHz
Test#2 (FP)
2863 points/GHz
5571 points/GHz
Test#3 (Generic, ZIP)
1117 points/GHz
2595 points/GHz
Test#1 (Memory)
1112 points/GHz
2242 points/GHz
TOTAL
8032 points/GHz
14007 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