| | | | | | |

Core i5-3210M vs i3-5005U


Description
The i5-3210M is based on Ivy Bridge architecture while the i3-5005U is based on Broadwell.

Using the multithread performance as a reference, the i5-3210M gets a score of 51.7 k points while the i3-5005U gets 47.9 k points.

Summarizing, the i5-3210M is 1.1 times faster than the i3-5005U . To get a proper comparison between both models, take a look to the data shown below.

Specs
CPUID
306a9
306d4
Core
Ivy Bridge
Broadwell-U
Architecture
Base frecuency
2.5 GHz
2 GHz
Boost frecuency
3.1 GHz
2 GHz
Socket
Socket G2 (988B)
Cores/Threads
2 /2
2 /2
TDP
35 W
15 W
Cache L1 (d+i)
2x32+2x32 kB
2x32+2x32 kB
Cache L2
2x256 kB
256 kB
Cache L3
3072 kB
3072 kB
Date
June 2012
March 2015
Mean monothread perf.
24.9k points
25.61k points
Mean multithread perf.
51.73k points
54.99k points

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
i3-5005U
Test#1 (Integers)
9.11k
6.24k (x0.68)
Test#2 (FP)
8.88k
8.82k (x0.99)
Test#3 (Generic, ZIP)
3.46k
2.38k (x0.69)
Test#1 (Memory)
3.45k
2.4k (x0.7)
TOTAL
24.9k
19.84k (x0.8)

Multithread

i5-3210M

i3-5005U
Test#1 (Integers)
18.72k
12.33k (x0.66)
Test#2 (FP)
21.09k
25.82k (x1.22)
Test#3 (Generic, ZIP)
8.38k
6.56k (x0.78)
Test#1 (Memory)
3.54k
3.18k (x0.9)
TOTAL
51.73k
47.89k (x0.93)

Performance/W
i5-3210M
i3-5005U
Test#1 (Integers)
535 points/W
822 points/W
Test#2 (FP)
603 points/W
1721 points/W
Test#3 (Generic, ZIP)
239 points/W
437 points/W
Test#1 (Memory)
101 points/W
212 points/W
TOTAL
1478 points/W
3193 points/W

Performance/GHz
i5-3210M
i3-5005U
Test#1 (Integers)
2939 points/GHz
3118 points/GHz
Test#2 (FP)
2863 points/GHz
4411 points/GHz
Test#3 (Generic, ZIP)
1117 points/GHz
1189 points/GHz
Test#1 (Memory)
1112 points/GHz
1201 points/GHz
TOTAL
8032 points/GHz
9920 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