Notebookcheck Logo

Texas Instruments OMAP 4470 vs Apple A5 vs Texas Instruments OMAP 4460

Texas Instruments OMAP 4470

► remove from comparison  OMAP 4470

Der Texas Instruments (TI) OMAP 4470 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.3-1.8 GHz und ARMs SIMD Engine NEON. Zusätzlich sind zwei ARM Cortex-M3 Kerne  Die integrierte PowerVR SGX540 Grafikkarte wird mit 277-384 MHz getaktet und kann wie die zwei Prozessorkerne auf den Dual Channel LPDDR2 Speicherkontroller (max 400MHz) zugreifen. Weiters ist eine Vivante CGPU für 2D Aufgaben verbaut. Im Vergleich zum OMAP 4430, ist beim 4460 daher CPU und GPU Teil höher getaktet.

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.

 

ModelTexas Instruments OMAP 4470Apple A5Texas Instruments OMAP 4460
Series Apple
CodenameCortex A9Cortex A9Cortex A9
Serie: Cortex A9
» Texas Instruments OMAP 44701.5 GHz2 / 2 Cortex A9
Texas Instruments OMAP 44601.2 GHz2 / 2 Cortex A9
Broadcom BCM281551.2 GHz2 / 2 Cortex A9
Texas Instruments OMAP 44301 GHz2 / 2 Cortex A9
Apple A5x1 GHz2 Cortex A9
Apple A51 GHz2 Cortex A9
Texas Instruments OMAP 44701.5 GHz2 / 2 Cortex A9
Texas Instruments OMAP 44601.2 GHz2 / 2 Cortex A9
Broadcom BCM281551.2 GHz2 / 2 Cortex A9
Texas Instruments OMAP 44301 GHz2 / 2 Cortex A9
Apple A5x1 GHz2 Cortex A9
» Apple A51 GHz2 Cortex A9
Texas Instruments OMAP 44701.5 GHz2 / 2 Cortex A9
» Texas Instruments OMAP 44601.2 GHz2 / 2 Cortex A9
Broadcom BCM281551.2 GHz2 / 2 Cortex A9
Texas Instruments OMAP 44301 GHz2 / 2 Cortex A9
Apple A5x1 GHz2 Cortex A9
Apple A51 GHz2 Cortex A9
Clock1500 MHz1000 MHz1200 MHz
L1 Cache1 MB1 MB
Cores / Threads2 / 222 / 2
Technology45 nm40, 32 nm45 nm
FeaturesDual Channel LPDDR 400MHz Memory Controller, IVA 3 Multimedia Accelerator, PowerVR SGX 540 Graphics Core, Image Signal ProcessorDual Channel LPDDR 400MHz Memory Controller, IVA 3 Multimedia Accelerator, PowerVR SGX 540 Graphics Core, Image Signal Processor
ArchitectureARMARMARM
Announced
TDP0.6 Watt

Benchmarks

Geekbench 3 - Geekbench 3 32 Bit Multi-Core
796 Points (1%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
427 Points (8%)
Geekbench 2 - 32 Bit - Geekbench Stream
min: 436     avg: 438     median: 438 (4%)     max: 440 Points
74%
A5 +
min: 297     avg: 317.7     median: 323 (3%)     max: 333 Points
min: 418     avg: 426     median: 426 (3%)     max: 434 Points
Geekbench 2 - 32 Bit - Geekbench Memory
min: 1302     avg: 1326     median: 1325.5 (12%)     max: 1349 Points
63%
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
min: 1895     avg: 1929     median: 1929 (4%)     max: 1963 Points
47%
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
min: 1118     avg: 1136     median: 1135.5 (2%)     max: 1153 Points
59%
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
min: 1367     avg: 1381     median: 1381 (4%)     max: 1395 Points
54%
A5 +
min: 631     avg: 715     median: 750 (2%)     max: 764 Points
min: 1137     avg: 1244     median: 1243.5 (3%)     max: 1350 Points
Linpack Android / IOS - Linpack Multi Thread
min: 80.5     avg: 87.6     median: 87.6 (3%)     max: 94.6 MFLOPS
145%
A5 +
min: 124.4     avg: 127.1     median: 127.1 (4%)     max: 129.8 MFLOPS
min: 73.8     avg: 75.2     median: 75.2 (3%)     max: 76.6 MFLOPS
Linpack Android / IOS - Linpack Single Thread
min: 52.5     avg: 55.4     median: 55.4 (5%)     max: 58.3 MFLOPS
148%
A5 +
min: 78.1     avg: 81.8     median: 81.8 (8%)     max: 85.4 MFLOPS
min: 44.38     avg: 48.6     median: 48.6 (5%)     max: 52.9 MFLOPS
Sunspider - Sunspider 0.9.1 Total Score *
min: 1438     avg: 1497     median: 1497 (14%)     max: 1556 ms
96%
A5 +
min: 1557     avg: 1863     median: 1888.5 (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: 2747     avg: 3447     median: 3447 (8%)     max: 4147 points
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 Texas Instruments OMAP 4470 → 100% n=8

Average Benchmarks Apple A5 → 86% n=8

Average Benchmarks Texas Instruments OMAP 4460 → 91% 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

v1.18
log 07. 14:24:26

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

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

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

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

#4 did not recreate cache, as it is less than 5 days old! Created at Wed, 05 Oct 2022 13:14:23 +0200 +0s ... 0s

#5 linkCache_getLink no uid found +0.004s ... 0.005s

#6 linkCache_getLink no uid found +0.06s ... 0.065s

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

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

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

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

#11 linkCache_getLink no uid found +0.001s ... 0.066s

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

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

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

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

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

#17 composed specs +0s ... 0.067s

#18 did output specs +0s ... 0.067s

#19 getting avg benchmarks for device 3647 +0s ... 0.067s

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

#21 linkCache_getLink no uid found +0.001s ... 0.069s

#22 got single benchmarks 3647 +0.006s ... 0.075s

#23 getting avg benchmarks for device 2331 +0s ... 0.075s

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

#25 got single benchmarks 2331 +0.007s ... 0.082s

#26 getting avg benchmarks for device 3601 +0s ... 0.082s

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

#28 got single benchmarks 3601 +0.007s ... 0.089s

#29 got avg benchmarks for devices +0s ... 0.089s

#30 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.09s

#31 linkCache_getLink no uid found +0s ... 0.09s

#32 linkCache_getLink no uid found +0s ... 0.091s

#33 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.091s

#34 linkCache_getLink no uid found +0s ... 0.091s

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

#36 linkCache_getLink no uid found +0s ... 0.092s

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

#38 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.092s

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

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

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

#42 linkCache_getLink no uid found +0s ... 0.092s

#43 linkCache_getLink no uid found +0s ... 0.093s

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

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

#46 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.093s

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

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

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

#50 linkCache_getLink no uid found +0s ... 0.093s

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

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

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

#54 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.094s

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

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

#57 linkCache_getLink no uid found +0s ... 0.094s

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

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

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

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

#62 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.096s

#63 linkCache_getLink no uid found +0s ... 0.096s

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

#65 linkCache_getLink no uid found +0s ... 0.096s

#66 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.096s

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

#68 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.097s

#69 linkCache_getLink no uid found +0s ... 0.097s

#70 linkCache_getLink no uid found +0s ... 0.097s

#71 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.097s

#72 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.097s

#73 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.097s

#74 linkCache_getLink no uid found +0.001s ... 0.098s

#75 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.098s

#76 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.098s

#77 linkCache_getLink no uid found +0s ... 0.098s

#78 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.098s

#79 linkCache_getLink no uid found +0s ... 0.098s

#80 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.098s

#81 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.099s

#82 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.099s

#83 linkCache_getLink no uid found +0s ... 0.099s

#84 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.099s

#85 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.099s

#86 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.099s

#87 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.1s

#88 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.1s

#89 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.1s

#90 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.101s

#91 min, max, avg, median took s +0s ... 0.101s

#92 return log +0s ... 0.101s

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