Notebookcheck Logo

Texas Instruments OMAP 4470 vs Apple A5x vs Texas Instruments OMAP 4430

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 A5x

► remove from comparison

Der Apple A5x ist ein Dual Core ARM Prozessor mit A9 basierenden Rechenkernen.  Im Kern integriert ist die relativ schnelle PowerVR SGX 543MP4 Quad-Core Grafikkarte. Verwendet wird der Chip ausschließlich im Apple iPad der 3. Generation.

Texas Instruments OMAP 4430

► remove from comparison  OMAP 4430

Der Texas Instruments (TI) OMAP 4430 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-1.2 GHz und ARMs SIMD Engine NEON. Zusätzlich sind zwei Cortex M3 Kerne für Multimediafunktionen integriert. Die integrierte PowerVR SGX540 Grafikkarte wird mit 304 MHz getaktet und kann wie die zwei Prozessorkerne auf den Dual Channel LPDDR2 Speicherkontroller (max 400MHz) zugreifen.

Die Performance der Rechenkerne liegt auf dem Niveau eines Nvidia Tegra 2 SoCs. Bei der Flash Performance im GUIMark 2 und Linpack Benchmarks unter Android liegen sie in etwas auf einem Level. Im Architektruvergleich fehlt dem Tegra 2 jedoch die SIMD Engine und auch das Speicher Interface ist nur als Single Channel ausgelegt.

Die Grafikperformance ist oft vergleichbar, wobei es Einzeltests gibt (RightWare Basemark ES 2.0) wo sich der SGX 540 deutlich durchsetzen kann.

Der Stromverbrauch ist mit angegebenen 100uW - 600mW relativ gering und eignet sich daher auch für den Einsatz in Smartphones.

ModelTexas Instruments OMAP 4470Apple A5xTexas Instruments OMAP 4430
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 MHz1000 MHz
L1 Cache1 MB1 MB
Cores / Threads2 / 222 / 2
Technology45 nm32? 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
Manufacturer OMAP 4430

Benchmarks

3DMark - 3DMark Ice Storm Physics
100%
1 A5x +
2858 Points (2%)
3DMark - 3DMark Ice Storm Extreme Physics
100%
1 A5x +
2865 Points (2%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Single-Core
100%
1 A5x +
330 Points (5%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Multi-Core
100%
1 A5x +
566 Points (1%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
100%
1 A5x +
496 Points (1%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
100%
1 A5x +
262 Points (5%)
Geekbench 2 - 32 Bit - Geekbench Stream
min: 436     avg: 438     median: 438 (4%)     max: 440 Points
76%
A5x +
333 Points (3%)
191 Points (2%)
Geekbench 2 - 32 Bit - Geekbench Memory
min: 1302     avg: 1326     median: 1325.5 (12%)     max: 1349 Points
62%
A5x +
818 Points (7%)
923 Points (8%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
min: 1895     avg: 1929     median: 1929 (4%)     max: 1963 Points
48%
A5x +
920 Points (2%)
183 Points (0%)
Geekbench 2 - 32 Bit - Geekbench Integer
min: 1118     avg: 1136     median: 1135.5 (2%)     max: 1153 Points
61%
A5x +
687 Points (1%)
449 Points (1%)
Geekbench 2 - 32 Bit - Geekbench Total Score
min: 1367     avg: 1381     median: 1381 (4%)     max: 1395 Points
55%
A5x +
759 Points (2%)
424 Points (1%)
Linpack Android / IOS - Linpack Multi Thread
min: 80.5     avg: 87.6     median: 87.6 (3%)     max: 94.6 MFLOPS
162%
A5x +
142 MFLOPS (5%)
min: 38.78     avg: 59.5     median: 63.7 (2%)     max: 71.9 MFLOPS
Linpack Android / IOS - Linpack Single Thread
min: 52.5     avg: 55.4     median: 55.4 (5%)     max: 58.3 MFLOPS
158%
A5x +
87.8 MFLOPS (9%)
min: 36.48     avg: 40.8     median: 40.6 (4%)     max: 45.39 MFLOPS
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
100%
1 A5x +
31272 ms (37%)
Sunspider - Sunspider 0.9.1 Total Score *
min: 1438     avg: 1497     median: 1497 (14%)     max: 1556 ms
99%
A5x +
min: 1329     avg: 1595     median: 1594.5 (15%)     max: 1860 ms
min: 1761     avg: 1955     median: 1895.5 (18%)     max: 2269 ms
Sunspider - Sunspider 1.0 Total Score *
100%
1 A5x +
1307 ms (14%)
Quadrant Standard Edition 2.0 - Quadrant Standard 2.0 Total Score
min: 2747     avg: 3447     median: 3447 (8%)     max: 4147 points
min: 2475     avg: 2571     median: 2571 (6%)     max: 2666 points
PassMark PerformanceTest Mobile V1 - PerformanceTest Mobile CPU Tests
100%
1 A5x +
11087 Points (1%)

Average Benchmarks Texas Instruments OMAP 4470 → 100% n=8

Average Benchmarks Apple A5x → 90% n=8

Average Benchmarks Texas Instruments OMAP 4430 → 54% 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 02. 12:46:33

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

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

#2 checking url part for id 3004 +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 Fri, 30 Sep 2022 13:14:19 +0200 +0s ... 0s

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

#6 linkCache_getLink no uid found +0.037s ... 0.041s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#23 getting avg benchmarks for device 3094 +0s ... 0.052s

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

#25 got single benchmarks 3094 +0.007s ... 0.058s

#26 getting avg benchmarks for device 3004 +0.001s ... 0.059s

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

#28 got single benchmarks 3004 +0.009s ... 0.068s

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

#30 linkCache_getLink using $NBC_LINKCACHE +0.006s ... 0.074s

#31 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.076s

#32 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.077s

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

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

#35 linkCache_getLink no uid found +0s ... 0.078s

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

#37 linkCache_getLink no uid found +0.001s ... 0.079s

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

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

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

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

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

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

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

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

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

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

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

#49 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.082s

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

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

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

#53 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.083s

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

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

#56 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.084s

#57 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.085s

#58 linkCache_getLink no uid found +0s ... 0.085s

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

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

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

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

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

#64 linkCache_getLink no uid found +0s ... 0.086s

#65 linkCache_getLink no uid found +0.001s ... 0.086s

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

#67 linkCache_getLink no uid found +0s ... 0.087s

#68 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.087s

#69 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.087s

#70 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.087s

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

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

#73 linkCache_getLink no uid found +0s ... 0.087s

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

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

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

#77 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.088s

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

#79 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.089s

#80 min, max, avg, median took s +0s ... 0.09s

#81 return log +0s ... 0.09s

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)