| | | | | | |

Core i5-3210M vs Pentium N5000


Description
The i5-3210M is based on Ivy Bridge architecture while the N5000 is based on Goldmont Plus.

Using the multithread performance as a reference, the i5-3210M gets a score of 53.7 k points while the N5000 gets 54.8 k points.

Summarizing, the N5000 is 1 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
706a1
Core
Ivy Bridge
Gemini Lake
Architecture
Base frecuency
2.5 GHz
1.1 GHz
Boost frecuency
3.1 GHz
2.7 GHz
Socket
Socket G2 (988B)
BGA 1090
Cores/Threads
2 /2
4/4
TDP
35 W
6 W
Cache L1 (d+i)
2x32+2x32 kB
4x32+4x24 kB
Cache L2
2x256 kB
4096 kB
Cache L3
3072 kB
0 kB
Date
June 2012
December 2017
Mean monothread perf.
24.9k points
17.27k points
Mean multithread perf.
51.73k points
54.76k 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
i5-3210M
N5000
Test#1 (Integers)
8.59k
5.12k (x0.6)
Test#2 (FP)
8.88k
7.66k (x0.86)
Test#3 (Generic, ZIP)
3.59k
2.79k (x0.78)
Test#1 (Memory)
3.45k
1.7k (x0.49)
TOTAL
24.51k
17.27k (x0.7)

Multithread

i5-3210M

N5000
Test#1 (Integers)
20.18k
17.56k (x0.87)
Test#2 (FP)
19.96k
25.71k (x1.29)
Test#3 (Generic, ZIP)
8.93k
9.45k (x1.06)
Test#1 (Memory)
4.6k
2.05k (x0.45)
TOTAL
53.67k
54.76k (x1.02)

Performance/W
i5-3210M
N5000
Test#1 (Integers)
577 points/W
2927 points/W
Test#2 (FP)
570 points/W
4284 points/W
Test#3 (Generic, ZIP)
255 points/W
1574 points/W
Test#1 (Memory)
131 points/W
341 points/W
TOTAL
1533 points/W
9127 points/W

Performance/GHz
i5-3210M
N5000
Test#1 (Integers)
2772 points/GHz
1895 points/GHz
Test#2 (FP)
2864 points/GHz
2838 points/GHz
Test#3 (Generic, ZIP)
1157 points/GHz
1032 points/GHz
Test#1 (Memory)
1114 points/GHz
631 points/GHz
TOTAL
7908 points/GHz
6396 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