, , , , , ,
zu verknüpfen.
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
 

Apple A5 vs Texas Instruments OMAP 4460

Apple A5

► remove from comparison

Der Apple A5 ist ein Dual Core ARM Prozessor mit Corex A9 basierenden Rechenkernen. Sie sind beide im iPad 2 und iPad Mini mit maximal 1000 MHz getaktet. Im iPhone jedoch nur mit 900 Mhz. Im SoC integriert ist die relativ schnelle PowerVR SGX 543MP2 Grafikkarte. Im selben Package befinden sich 512MB RAM (beim iPad 2).

Verwendet wird der Chip z.B. beim Apple iPad 2, 2,5 und iPhone 4s Tablet und Apple wirbt mit bis zu 2x Rechenleistung im Vergleich zum 1 GHz A4 Single Core. Gefertigt wurde der A5 anfangs noch in 40nm. Mit dem erscheinen des iPad 3, kam im iPad 2 aber eine 32nm Variante zum Einsatz, welche wahrscheinlich auch im iPad Mini eingesetzt wird.

Texas Instruments OMAP 4460

► remove from comparison  OMAP 4460

Der Texas Instruments (TI) OMAP 4460 ist ein SoC (System on a Chip) für Handys und Tablet PCs. Er beinhaltet zwei ARM Cortex-A9 (ARM v7 Instruction Set) Rechenkernen mit 1.2-1.5 GHz und ARMs SIMD Engine NEON. Die integrierte PowerVR SGX540 Grafikkarte wird mit 384 MHz getaktet und kann wie die zwei Prozessorkerne auf den Dual Channel LPDDR2 Speicherkontroller (max 400MHz) zugreifen. Im Vergleich zum OMAP 4430, ist beim 4460 daher CPU und GPU Teil höher getaktet.

 

ModelApple A5Texas Instruments OMAP 4460
SeriesApple
CodenameCortex A9Cortex A9
Serie: Cortex A9
Texas Instruments OMAP 4470 compare1.5 GHz2 / 2 Cortex A9
Texas Instruments OMAP 44601.2 GHz2 / 2 Cortex A9
Broadcom BCM28155 compare1.2 GHz2 / 2 Cortex A9
Texas Instruments OMAP 4430 compare1 GHz2 / 2 Cortex A9
Apple A5x compare1 GHz2 Cortex A9
» Apple A51 GHz2 Cortex A9
Texas Instruments OMAP 4470 compare1.5 GHz2 / 2 Cortex A9
» Texas Instruments OMAP 44601.2 GHz2 / 2 Cortex A9
Broadcom BCM28155 compare1.2 GHz2 / 2 Cortex A9
Texas Instruments OMAP 4430 compare1 GHz2 / 2 Cortex A9
Apple A5x compare1 GHz2 Cortex A9
Apple A51 GHz2 Cortex A9
Clock1000 MHz1200 MHz
Cores / Threads22 / 2
Technology40, 32 nm45 nm
ArchitectureARMARM
Announced
L1 Cache1 MB
TDP0.6 Watt
FeaturesDual Channel LPDDR 400MHz Memory Controller, IVA 3 Multimedia Accelerator, PowerVR SGX 540 Graphics Core, Image Signal Processor

Benchmarks

Geekbench 2 - 32 Bit - Geekbench Stream
100%
A5 +
min: 297     avg: 318     median: 323 (3%)     max: 333 Points
min: 418     avg: 426     median: 426 (3%)     max: 434 Points
Geekbench 2 - 32 Bit - Geekbench Memory
100%
A5 +
min: 751     avg: 807     median: 833 (8%)     max: 838 Points
min: 1123     avg: 1207     median: 1206.5 (11%)     max: 1290 Points
Geekbench 2 - 32 Bit - Geekbench Floating Point
100%
A5 +
min: 737     avg: 855     median: 906 (2%)     max: 923 Points
min: 1573     avg: 1730     median: 1730 (3%)     max: 1887 Points
Geekbench 2 - 32 Bit - Geekbench Integer
100%
A5 +
min: 552     avg: 638     median: 671 (1%)     max: 691 Points
min: 917     avg: 1013     median: 1013 (2%)     max: 1109 Points
Geekbench 2 - 32 Bit - Geekbench Total Score
100%
A5 +
min: 631     avg: 715     median: 750 (2%)     max: 764 Points
min: 1137     avg: 1244     median: 1243.5 (3%)     max: 1350 Points
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
796 Points (1%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
427 Points (9%)
Linpack Android / IOS - Linpack Multi Thread
100%
A5 +
min: 124.4     avg: 127     median: 127.1 (4%)     max: 129.84 MFLOPS
min: 73.782     avg: 75.2     median: 75.2 (3%)     max: 76.562 MFLOPS
Linpack Android / IOS - Linpack Single Thread
100%
A5 +
min: 78.14     avg: 81.8     median: 81.8 (8%)     max: 85.4 MFLOPS
min: 44.379     avg: 48.6     median: 48.6 (5%)     max: 52.858 MFLOPS
Sunspider - Sunspider 0.9.1 Total Score *
100%
A5 +
min: 1556.8     avg: 1863     median: 1888.6 (18%)     max: 2118 ms
min: 1102     avg: 1445     median: 1444.5 (14%)     max: 1787 ms
Sunspider - Sunspider 1.0 Total Score *
1096 ms (12%)
Quadrant Standard Edition 2.0 - Quadrant Standard 2.0 Total Score
min: 2226     avg: 2586     median: 2585.5 (6%)     max: 2945 points
AnTuTu v4 - AnTuTu v4 Total Score
12347 Points (29%)
AndEBench - AndEBench Java
224 Iter./s (7%)
AndEBench - AndEBench Native
5481 Iter./s (18%)
PassMark PerformanceTest Mobile V1 - PerformanceTest Mobile CPU Tests
5787 Points (1%)

Average Benchmarks Apple A5 → 100% n=8

Average Benchmarks Texas Instruments OMAP 4460 → 126% n=8

- Bereich der Benchmarkergebnisse für diese Grafikkarte
- Durchschnittliche Benchmarkergebnisse für diese Grafikkarte
* Smaller numbers mean a higher performance
1 This benchmark is not used for the average calculation

Add one or more devices and compare

In the following list you can select (and also search for) devices that should be added to the comparison. You can select more than one device.

restrict list:

show all (including archived), 2022, 2021
v1.17
log 27. 16:11:33

#0 checking url part for id 2331 +0s ... 0s

#1 checking url part for id 3601 +0s ... 0s

#2 not redirecting to Ajax server +0s ... 0s

#3 did not recreate cache, as it is less than 5 days old! Created at Sun, 23 Jan 2022 12:10:51 +0100 +0s ... 0s

#4 linkCache_getLink no uid found +0.002s ... 0.003s

#5 linkCache_getLink using $NBC_LINKCACHE +0.04s ... 0.043s

#6 linkCache_getLink no uid found +0.005s ... 0.047s

#7 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.047s

#8 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#9 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#10 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#11 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#12 composed specs +0s ... 0.048s

#13 did output specs +0s ... 0.048s

#14 getting avg benchmarks for device 2331 +0s ... 0.048s

#15 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#16 got single benchmarks 2331 +0.008s ... 0.057s

#17 getting avg benchmarks for device 3601 +0s ... 0.057s

#18 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#19 linkCache_getLink no uid found +0.001s ... 0.059s

#20 got single benchmarks 3601 +0.005s ... 0.064s

#21 got avg benchmarks for devices +0s ... 0.064s

#22 linkCache_getLink no uid found +0s ... 0.064s

#23 linkCache_getLink no uid found +0.001s ... 0.065s

#24 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.065s

#25 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.065s

#26 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.066s

#27 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.066s

#28 linkCache_getLink no uid found +0s ... 0.066s

#29 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.066s

#30 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.066s

#31 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.066s

#32 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.066s

#33 linkCache_getLink no uid found +0s ... 0.066s

#34 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.066s

#35 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.066s

#36 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.067s

#37 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.067s

#38 linkCache_getLink no uid found +0s ... 0.067s

#39 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.067s

#40 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.067s

#41 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.067s

#42 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.067s

#43 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.068s

#44 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.068s

#45 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.068s

#46 linkCache_getLink no uid found +0s ... 0.068s

#47 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.068s

#48 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.068s

#49 linkCache_getLink no uid found +0s ... 0.069s

#50 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.069s

#51 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.069s

#52 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.069s

#53 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.069s

#54 linkCache_getLink no uid found +0s ... 0.069s

#55 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.069s

#56 linkCache_getLink no uid found +0s ... 0.069s

#57 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.069s

#58 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.069s

#59 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.07s

#60 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.07s

#61 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.07s

#62 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.07s

#63 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.071s

#64 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.071s

#65 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.071s

#66 min, max, avg, median took s +0s ... 0.071s

#67 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.072s

#68 return log +0.004s ... 0.075s

Teilen Sie diesen Artikel um uns zu unterstützen. Jeder Link hilft!
> Notebook Test, Laptop Test und News > Benchmarks / Technik > Benchmarks / Technik > Prozessor Vergleich - Head 2 Head
Autor: Redaktion,  8.09.2017 (Update: 19.05.2020)