| | | | | | |

Core i5-3317U vs i5-2410M


Description
The i5-3317U is based on Ivy Bridge architecture while the i5-2410M is based on Sandy Bridge.

Using the multithread performance as a reference, the i5-3317U gets a score of 41.3 k points while the i5-2410M gets 38.7 k points.

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

Specs
CPUID
306a9
206a7
Core
Ivy Bridge
Sandy Bridge
Architecture
Base frecuency
1.7 GHz
2.3 GHz
Boost frecuency
2.6 GHz
2.9 GHz
Socket
BGA1023
Socket G2 (988B)
Cores/Threads
2 /2
2/2
TDP
17 W
35 W
Cache L1 (d+i)
2x32+2x32 kB
2x32+2x32 kB
Cache L2
2x256 kB
2x256 kB
Cache L3
3072 kB
3072 kB
Date
June 2012
February 2011
Mean monothread perf.
17.88k points
20.1k points
Mean multithread perf.
41.31k points
38.68k 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-3317U
i5-2410M
Test#1 (Integers)
2.5k
2.38k (x0.95)
Test#2 (FP)
7.18k
6.6k (x0.92)
Test#3 (Generic, ZIP)
3.19k
3.48k (x1.09)
Test#1 (Memory)
3.41k
3.16k (x0.93)
TOTAL
16.27k
15.62k (x0.96)

Multithread

i5-3317U

i5-2410M
Test#1 (Integers)
4.93k
5.49k (x1.11)
Test#2 (FP)
15.72k
14.39k (x0.92)
Test#3 (Generic, ZIP)
7.53k
8.39k (x1.11)
Test#1 (Memory)
4.21k
3.09k (x0.73)
TOTAL
32.39k
31.35k (x0.97)

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-3317U
i5-2410M
Test#1 (Integers)
8.38k
7.98k (x0.95)
Test#2 (FP)
7.76k
6.55k (x0.84)
Test#3 (Generic, ZIP)
3.33k
3.28k (x0.99)
Test#1 (Memory)
3.41k
2.7k (x0.79)
TOTAL
22.88k
20.52k (x0.9)

Multithread

i5-3317U

i5-2410M
Test#1 (Integers)
16.56k
13.66k (x0.82)
Test#2 (FP)
16.79k
13.17k (x0.78)
Test#3 (Generic, ZIP)
7.85k
7.05k (x0.9)
Test#1 (Memory)
4.02k
3.02k (x0.75)
TOTAL
45.23k
36.9k (x0.82)

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-3317U
i5-2410M
Test#1 (Integers)
6.11k
7.38k (x1.21)
Test#2 (FP)
6.58k
6.76k (x1.03)
Test#3 (Generic, ZIP)
2.48k
3.3k (x1.33)
Test#1 (Memory)
2.71k
2.66k (x0.98)
TOTAL
17.88k
20.1k (x1.12)

Multithread

i5-3317U

i5-2410M
Test#1 (Integers)
13.67k
14.17k (x1.04)
Test#2 (FP)
16.8k
14.71k (x0.88)
Test#3 (Generic, ZIP)
6.66k
6.93k (x1.04)
Test#1 (Memory)
4.17k
2.87k (x0.69)
TOTAL
41.31k
38.68k (x0.94)

Performance/W
i5-3317U
i5-2410M
Test#1 (Integers)
804 points/W
405 points/W
Test#2 (FP)
988 points/W
420 points/W
Test#3 (Generic, ZIP)
392 points/W
198 points/W
Test#1 (Memory)
246 points/W
82 points/W
TOTAL
2430 points/W
1105 points/W

Performance/GHz
i5-3317U
i5-2410M
Test#1 (Integers)
2351 points/GHz
2543 points/GHz
Test#2 (FP)
2532 points/GHz
2332 points/GHz
Test#3 (Generic, ZIP)
953 points/GHz
1139 points/GHz
Test#1 (Memory)
1043 points/GHz
917 points/GHz
TOTAL
6879 points/GHz
6932 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