| | | | | | |

Core i5-3210M vs Ryzen 5 2400G


Description
The i5-3210M is based on Ivy Bridge architecture while the 2400G is based on Zen.

Using the multithread performance as a reference, the i5-3210M gets a score of 51.7 k points while the 2400G gets 188.5 k points.

Summarizing, the 2400G is 3.6 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
810f10
Core
Ivy Bridge
Raven Ridge
Architecture
Base frecuency
2.5 GHz
3.6 GHz
Boost frecuency
3.1 GHz
3.9 GHz
Socket
Socket G2 (988B)
AM4
Cores/Threads
2 /2
4/8
TDP
35 W
65 W
Cache L1 (d+i)
2x32+2x32 kB
4x64+4x32 kB
Cache L2
2x256 kB
4x512 kB
Cache L3
3072 kB
4096 kB
Date
June 2012
January 2018
Mean monothread perf.
24.9k points
47.96k points
Mean multithread perf.
51.73k points
198.27k 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
2400G
Test#1 (Integers)
3.08k
3.8k (x1.23)
Test#2 (FP)
8.58k
17.38k (x2.03)
Test#3 (Generic, ZIP)
3.76k
5.17k (x1.37)
Test#1 (Memory)
3.99k
3.16k (x0.79)
TOTAL
19.42k
29.52k (x1.52)

Multithread

i5-3210M

2400G
Test#1 (Integers)
5.79k
15.28k (x2.64)
Test#2 (FP)
18.77k
76.44k (x4.07)
Test#3 (Generic, ZIP)
8.74k
27.48k (x3.14)
Test#1 (Memory)
4.59k
3.02k (x0.66)
TOTAL
37.89k
122.2k (x3.23)

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
2400G
Test#1 (Integers)
8.59k
13.95k (x1.62)
Test#2 (FP)
8.88k
20.7k (x2.33)
Test#3 (Generic, ZIP)
3.59k
5.33k (x1.49)
Test#1 (Memory)
3.45k
3.03k (x0.88)
TOTAL
24.51k
43.01k (x1.75)

Multithread

i5-3210M

2400G
Test#1 (Integers)
20.18k
58.56k (x2.9)
Test#2 (FP)
19.96k
92.95k (x4.66)
Test#3 (Generic, ZIP)
8.93k
28.55k (x3.2)
Test#1 (Memory)
4.6k
2.98k (x0.65)
TOTAL
53.67k
183.04k (x3.41)

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
2400G
Test#1 (Integers)
9.11k
13.04k (x1.43)
Test#2 (FP)
8.88k
22.35k (x2.52)
Test#3 (Generic, ZIP)
3.46k
5.37k (x1.55)
Test#1 (Memory)
3.45k
3.4k (x0.99)
TOTAL
24.9k
44.15k (x1.77)

Multithread

i5-3210M

2400G
Test#1 (Integers)
18.72k
56.49k (x3.02)
Test#2 (FP)
21.09k
100.74k (x4.78)
Test#3 (Generic, ZIP)
8.38k
28.21k (x3.37)
Test#1 (Memory)
3.54k
3.04k (x0.86)
TOTAL
51.73k
188.49k (x3.64)

Performance/W
i5-3210M
2400G
Test#1 (Integers)
535 points/W
869 points/W
Test#2 (FP)
603 points/W
1550 points/W
Test#3 (Generic, ZIP)
239 points/W
434 points/W
Test#1 (Memory)
101 points/W
47 points/W
TOTAL
1478 points/W
2900 points/W

Performance/GHz
i5-3210M
2400G
Test#1 (Integers)
2939 points/GHz
3343 points/GHz
Test#2 (FP)
2863 points/GHz
5731 points/GHz
Test#3 (Generic, ZIP)
1117 points/GHz
1376 points/GHz
Test#1 (Memory)
1112 points/GHz
871 points/GHz
TOTAL
8032 points/GHz
11321 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