Notebookcheck Logo

Apple A5x vs Texas Instruments OMAP 4470

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 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.

ModelApple A5xTexas Instruments OMAP 4470
SeriesApple
CodenameCortex A9Cortex A9
Serie: Cortex A9
Texas Instruments OMAP 44701.5 GHz2 / 2 Cortex A9
Texas Instruments OMAP 4460 compare1.2 GHz2 / 2 Cortex A9
Broadcom BCM28155 compare1.2 GHz2 / 2 Cortex A9
Texas Instruments OMAP 4430 compare1 GHz2 / 2 Cortex A9
» Apple A5x1 GHz2 Cortex A9
Apple A5 compare1 GHz2 Cortex A9
» Texas Instruments OMAP 44701.5 GHz2 / 2 Cortex A9
Texas Instruments OMAP 4460 compare1.2 GHz2 / 2 Cortex A9
Broadcom BCM28155 compare1.2 GHz2 / 2 Cortex A9
Texas Instruments OMAP 4430 compare1 GHz2 / 2 Cortex A9
Apple A5x1 GHz2 Cortex A9
Apple A5 compare1 GHz2 Cortex A9
Clock1000 MHz1500 MHz
Cores / Threads22 / 2
Technology32? nm45 nm
ArchitectureARMARM
Announced
L1 Cache1 MB
FeaturesDual Channel LPDDR 400MHz Memory Controller, IVA 3 Multimedia Accelerator, PowerVR SGX 540 Graphics Core, Image Signal Processor

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
100%
A5x +
333 Points (3%)
min: 436     avg: 438     median: 438 (4%)     max: 440 Points
Geekbench 2 - 32 Bit - Geekbench Memory
100%
A5x +
818 Points (7%)
min: 1302     avg: 1326     median: 1325.5 (12%)     max: 1349 Points
Geekbench 2 - 32 Bit - Geekbench Floating Point
100%
A5x +
920 Points (2%)
min: 1895     avg: 1929     median: 1929 (4%)     max: 1963 Points
Geekbench 2 - 32 Bit - Geekbench Integer
100%
A5x +
687 Points (1%)
min: 1118     avg: 1136     median: 1135.5 (2%)     max: 1153 Points
Geekbench 2 - 32 Bit - Geekbench Total Score
100%
A5x +
759 Points (2%)
min: 1367     avg: 1381     median: 1381 (4%)     max: 1395 Points
Linpack Android / IOS - Linpack Multi Thread
100%
A5x +
142 MFLOPS (5%)
min: 80.5     avg: 87.6     median: 87.6 (3%)     max: 94.6 MFLOPS
Linpack Android / IOS - Linpack Single Thread
100%
A5x +
87.8 MFLOPS (9%)
min: 52.5     avg: 55.4     median: 55.4 (5%)     max: 58.3 MFLOPS
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
100%
1 A5x +
31272 ms (37%)
Sunspider - Sunspider 1.0 Total Score *
100%
1 A5x +
1307 ms (14%)
Sunspider - Sunspider 0.9.1 Total Score *
100%
A5x +
min: 1329     avg: 1595     median: 1594.5 (15%)     max: 1860 ms
min: 1438     avg: 1497     median: 1497 (14%)     max: 1556 ms
Quadrant Standard Edition 2.0 - Quadrant Standard 2.0 Total Score
min: 2747     avg: 3447     median: 3447 (8%)     max: 4147 points
PassMark PerformanceTest Mobile V1 - PerformanceTest Mobile CPU Tests
100%
1 A5x +
11087 Points (1%)

Average Benchmarks Apple A5x → 100% n=8

Average Benchmarks Texas Instruments OMAP 4470 → 135% 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.18
log 07. 07:36:24

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

#1 checking url part for id 3647 +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 Wed, 05 Oct 2022 13:14:23 +0200 +0s ... 0s

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

#5 linkCache_getLink using $NBC_LINKCACHE +0.041s ... 0.042s

#6 linkCache_getLink no uid found +0.004s ... 0.046s

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

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

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

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

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

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

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

#14 getting avg benchmarks for device 3094 +0s ... 0.047s

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

#16 got single benchmarks 3094 +0.008s ... 0.055s

#17 getting avg benchmarks for device 3647 +0s ... 0.055s

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

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

#20 got single benchmarks 3647 +0.006s ... 0.063s

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

#22 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.064s

#23 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.064s

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

#25 linkCache_getLink no uid found +0s ... 0.065s

#26 linkCache_getLink no uid found +0s ... 0.065s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#48 linkCache_getLink no uid found +0s ... 0.07s

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

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

#51 linkCache_getLink no uid found +0s ... 0.07s

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

#53 linkCache_getLink no uid found +0s ... 0.071s

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

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

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

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

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

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)