Notebookcheck Logo

Texas Instruments OMAP 4460 vs Texas Instruments OMAP 4430 vs Apple A5

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.

 

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.

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.

ModelTexas Instruments OMAP 4460Texas Instruments OMAP 4430Apple A5
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
Clock1200 MHz1000 MHz1000 MHz
L1 Cache1 MB1 MB
Cores / Threads2 / 22 / 22
TDP0.6 Watt0.6 Watt
Technology45 nm45 nm40, 32 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
Manufacturer OMAP 4430

Benchmarks

Geekbench 3 - Geekbench 3 32 Bit Multi-Core
796 Points (1%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
427 Points (9%)
Geekbench 2 - 32 Bit - Geekbench Stream
min: 418     avg: 426     median: 426 (3%)     max: 434 Points
191 Points (2%)
76%
A5 +
min: 297     avg: 317.7     median: 323 (3%)     max: 333 Points
Geekbench 2 - 32 Bit - Geekbench Memory
min: 1123     avg: 1207     median: 1206.5 (11%)     max: 1290 Points
923 Points (8%)
69%
A5 +
min: 751     avg: 807     median: 833 (8%)     max: 838 Points
Geekbench 2 - 32 Bit - Geekbench Floating Point
min: 1573     avg: 1730     median: 1730 (3%)     max: 1887 Points
183 Points (0%)
52%
A5 +
min: 737     avg: 855     median: 906 (2%)     max: 923 Points
Geekbench 2 - 32 Bit - Geekbench Integer
min: 917     avg: 1013     median: 1013 (2%)     max: 1109 Points
449 Points (1%)
66%
A5 +
min: 552     avg: 638     median: 671 (1%)     max: 691 Points
Geekbench 2 - 32 Bit - Geekbench Total Score
min: 1137     avg: 1244     median: 1243.5 (3%)     max: 1350 Points
424 Points (1%)
60%
A5 +
min: 631     avg: 715     median: 750 (2%)     max: 764 Points
Linpack Android / IOS - Linpack Multi Thread
min: 73.8     avg: 75.2     median: 75.2 (3%)     max: 76.6 MFLOPS
min: 38.78     avg: 59.5     median: 63.7 (2%)     max: 71.9 MFLOPS
169%
A5 +
min: 124.4     avg: 127.1     median: 127.1 (4%)     max: 129.8 MFLOPS
Linpack Android / IOS - Linpack Single Thread
min: 44.38     avg: 48.6     median: 48.6 (5%)     max: 52.9 MFLOPS
min: 36.48     avg: 40.8     median: 40.6 (4%)     max: 45.39 MFLOPS
168%
A5 +
min: 78.1     avg: 81.8     median: 81.8 (8%)     max: 85.4 MFLOPS
Sunspider - Sunspider 1.0 Total Score *
1096 ms (12%)
Sunspider - Sunspider 0.9.1 Total Score *
min: 1102     avg: 1445     median: 1444.5 (14%)     max: 1787 ms
min: 1761     avg: 1955     median: 1895.5 (18%)     max: 2269 ms
95%
A5 +
min: 1557     avg: 1863     median: 1888.5 (18%)     max: 2118 ms
Quadrant Standard Edition 2.0 - Quadrant Standard 2.0 Total Score
min: 2226     avg: 2586     median: 2585.5 (6%)     max: 2945 points
min: 2475     avg: 2571     median: 2571 (6%)     max: 2666 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 4460 → 100% n=8

Average Benchmarks Texas Instruments OMAP 4430 → 59% n=8

Average Benchmarks Apple A5 → 94% 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.17
log 06. 03:13:24

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

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

#2 checking url part for id 2331 +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 Sat, 02 Jul 2022 13:13:02 +0200 +0s ... 0s

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

#6 linkCache_getLink no uid found +0.058s ... 0.063s

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

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

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

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

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

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

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

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

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

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

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

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

#19 getting avg benchmarks for device 3601 +0s ... 0.064s

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

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

#22 got single benchmarks 3601 +0.006s ... 0.072s

#23 getting avg benchmarks for device 3004 +0s ... 0.073s

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

#25 got single benchmarks 3004 +0.008s ... 0.08s

#26 getting avg benchmarks for device 2331 +0s ... 0.081s

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

#28 got single benchmarks 2331 +0.006s ... 0.087s

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

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

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

#32 linkCache_getLink no uid found +0.001s ... 0.089s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#68 linkCache_getLink no uid found +0s ... 0.095s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#88 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.099s

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

#90 min, max, avg, median took s +0s ... 0.099s

#91 return log +0s ... 0.099s

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)