Notebookcheck Logo
, , , , , ,
zu verknüpfen.
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
 

Broadcom BCM28155 vs Texas Instruments OMAP 4470

Broadcom BCM28155

► remove from comparison Broadcom BCM28155

Der Broadcom BCM28155 ist ein Dual-Core Cortex-A9 SoC mit einer VideoCore-IV Grafikkarte. Mit 1.2 GHz Taktrate findet man den BCM28155 z.B. im Galaxy S II Plus. Das integrierte Modem unterstützt UMTS und HSPA+, jedoch kein LTE.

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.

show full text
ModelBroadcom BCM28155Texas Instruments OMAP 4470
SeriesBroadcom
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 BCM281551.2 GHz2 / 2 Cortex A9
Texas Instruments OMAP 4430 compare1 GHz2 / 2 Cortex A9
Apple A5x compare1 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 BCM281551.2 GHz2 / 2 Cortex A9
Texas Instruments OMAP 4430 compare1 GHz2 / 2 Cortex A9
Apple A5x compare1 GHz2 Cortex A9
Apple A5 compare1 GHz2 Cortex A9
Clock1200 MHz1500 MHz
Cores / Threads2 / 22 / 2
Technology40 nm45 nm
FeaturesDual Channel LPDDR2 400MHz Memory Controller, VideoCore-IV GPUDual Channel LPDDR 400MHz Memory Controller, IVA 3 Multimedia Accelerator, PowerVR SGX 540 Graphics Core, Image Signal Processor
ArchitectureARMARM
Announced
ManufacturerBroadcom BCM28155
L1 Cache1 MB

Benchmarks

Geekbench 2 - 32 Bit - Geekbench Stream
min: 149     avg: 240.5     median: 240.5 (2%)     max: 332 Points
min: 436     avg: 438     median: 438 (4%)     max: 440 Points
Geekbench 2 - 32 Bit - Geekbench Memory
min: 731     avg: 738     median: 737.5 (7%)     max: 744 Points
min: 1302     avg: 1326     median: 1325.5 (12%)     max: 1349 Points
Geekbench 2 - 32 Bit - Geekbench Floating Point
min: 555     avg: 930     median: 930 (2%)     max: 1305 Points
min: 1895     avg: 1929     median: 1929 (4%)     max: 1963 Points
Geekbench 2 - 32 Bit - Geekbench Integer
min: 324     avg: 533     median: 533 (1%)     max: 742 Points
min: 1118     avg: 1136     median: 1135.5 (2%)     max: 1153 Points
Geekbench 2 - 32 Bit - Geekbench Total Score
min: 468     avg: 679     median: 679 (2%)     max: 890 Points
min: 1367     avg: 1381     median: 1381 (4%)     max: 1395 Points
Linpack Android / IOS - Linpack Multi Thread
min: 24.39     avg: 52     median: 52 (2%)     max: 79.7 MFLOPS
min: 80.5     avg: 87.6     median: 87.6 (3%)     max: 94.6 MFLOPS
Linpack Android / IOS - Linpack Single Thread
min: 26.08     avg: 36.2     median: 36.2 (4%)     max: 46.3 MFLOPS
min: 52.5     avg: 55.4     median: 55.4 (5%)     max: 58.3 MFLOPS
Sunspider - Sunspider 0.9.1 Total Score *
min: 1434     avg: 1701     median: 1701 (16%)     max: 1968 ms
min: 1438     avg: 1497     median: 1497 (14%)     max: 1556 ms
Quadrant Standard Edition 2.0 - Quadrant Standard 2.0 Total Score
3909 points (9%)
min: 2747     avg: 3447     median: 3447 (8%)     max: 4147 points
AnTuTu v3 - AnTuTu v3 CPU
min: 1169     avg: 1255     median: 1255 (8%)     max: 1341 Points

Average Benchmarks Broadcom BCM28155 → 100% n=9

Average Benchmarks Texas Instruments OMAP 4470 → 166% n=9

- 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 21. 09:03:20

#0 checking url part for id 3771 +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, 18 May 2022 13:12:25 +0200 +0s ... 0s

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

#5 linkCache_getLink using $NBC_LINKCACHE +0.049s ... 0.053s

#6 linkCache_getLink no uid found +0.003s ... 0.056s

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

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

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

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

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

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

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

#14 getting avg benchmarks for device 3771 +0s ... 0.056s

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

#16 got single benchmarks 3771 +0.007s ... 0.064s

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

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

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

#20 got single benchmarks 3647 +0.005s ... 0.071s

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

#22 linkCache_getLink no uid found +0.001s ... 0.072s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#52 linkCache_getLink no uid found +0s ... 0.076s

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

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

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

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

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

#58 return log +0.003s ... 0.08s

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)