Notebookcheck Logo

Amlogic AML8726-MX vs Loongson 2F 900MHz

Amlogic AML8726-MX

Der Amlogic AML8726-M ist ein günstiger SoC für Tablets und Smartphones aus 2012. Er integriert zwei ARM Cortex-A9 Kerne (max. 1,5 GHz) mit NEON Erweiterung und eine ARM Mali-400 MP2 Grafikkarte. Auch 1080p Video Dekodierung wird von dem Chip unterstützt.

Loongson 2F 900MHz

► remove from comparison

ModelAmlogic AML8726-MXLoongson 2F 900MHz
Series
Serie:
UNISOC Tiger T310 compare1.8 - 2 GHz4 / 4
Rockchip RK3288 compare1.8 GHz4 / 4
Apple A6x compare1.4 GHz2
Apple A6 compare1 GHz2
Apple S5 compare2 / 2
HiSilicon k3v2 Hi3620 compare1.2 GHz4 / 4
Rockchip RK3066 1.5 GHz compare1.5 GHz2 / 2
» Amlogic AML8726-MX1.5 GHz2 / 2
Rockchip RK3168 compare1.2 GHz2 / 2
Rockchip RK2918 1.2 GHz compare1.2 GHz1 / 1
ARM Cortex A8 1.2 GHz compare1.2 GHz1 / 1
Telechips TCC8803 1GHz compare1 GHz1 / 1
Loongson 2F 900MHz0.9 GHz1 / 1
CSR8670 compare0.08 GHz2
ARM Cortex-M4 compare
HiSilicon Hi6262 compare
DK3.5+ST compare2
unknown compare
UNISOC Tiger T310 compare1.8 - 2 GHz4 / 4
Rockchip RK3288 compare1.8 GHz4 / 4
Apple A6x compare1.4 GHz2
Apple A6 compare1 GHz2
Apple S5 compare2 / 2
HiSilicon k3v2 Hi3620 compare1.2 GHz4 / 4
Rockchip RK3066 1.5 GHz compare1.5 GHz2 / 2
Amlogic AML8726-MX1.5 GHz2 / 2
Rockchip RK3168 compare1.2 GHz2 / 2
Rockchip RK2918 1.2 GHz compare1.2 GHz1 / 1
ARM Cortex A8 1.2 GHz compare1.2 GHz1 / 1
Telechips TCC8803 1GHz compare1 GHz1 / 1
» Loongson 2F 900MHz0.9 GHz1 / 1
CSR8670 compare0.08 GHz2
ARM Cortex-M4 compare
HiSilicon Hi6262 compare
DK3.5+ST compare2
unknown compare
Clock1500 MHz900 MHz
L2 Cache512 KB512 KB
Cores / Threads2 / 21 / 1
Technology45 nm
FeaturesNEON, VFP, Cortex-A9
ArchitectureARMMIPS
Announced
Manufacturer AML8726-MX
TDP4 Watt

Benchmarks

Geekbench 2 - 32 Bit - Geekbench Stream
min: 267     avg: 268.5     median: 268.5 (2%)     max: 270 Points
Geekbench 2 - 32 Bit - Geekbench Memory
min: 958     avg: 963     median: 963 (9%)     max: 968 Points
Geekbench 2 - 32 Bit - Geekbench Floating Point
min: 1409     avg: 1451     median: 1450.5 (3%)     max: 1492 Points
Geekbench 2 - 32 Bit - Geekbench Integer
min: 825     avg: 840     median: 839.5 (2%)     max: 854 Points
Geekbench 2 - 32 Bit - Geekbench Total Score
min: 1000     avg: 1021     median: 1020.5 (3%)     max: 1041 Points
Linpack Android / IOS - Linpack Multi Thread
min: 63.9     avg: 86.6     median: 84.2 (3%)     max: 111.8 MFLOPS
Linpack Android / IOS - Linpack Single Thread
min: 50.7     avg: 57.9     median: 52.9 (5%)     max: 70.1 MFLOPS
Sunspider - Sunspider 0.9.1 Total Score *
min: 1243     avg: 1336     median: 1252 (12%)     max: 1513 ms
Quadrant Standard Edition 2.0 - Quadrant Standard 2.0 Total Score
min: 3947     avg: 4055     median: 4055 (9%)     max: 4163 points
AnTuTu v3 - AnTuTu v3 CPU
min: 4082     avg: 4886     median: 4886 (32%)     max: 5690 Points

Average Benchmarks Amlogic AML8726-MX → NAN% n=

- 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 09. 12:36:21

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

#1 checking url part for id 480 +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 Sat, 06 Aug 2022 13:13:32 +0200 +0s ... 0s

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

#5 linkCache_getLink no uid found +0s ... 0.002s

#6 linkCache_getLink no uid found +0.064s ... 0.066s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#36 getting avg benchmarks for device 3611 +0s ... 0.067s

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

#38 got single benchmarks 3611 +0.008s ... 0.076s

#39 getting avg benchmarks for device 480 +0s ... 0.076s

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

#41 got single benchmarks 480 +0.005s ... 0.082s

#42 got avg benchmarks for devices +0s ... 0.082s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#58 linkCache_getLink using $NBC_LINKCACHE +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 +0.001s ... 0.086s

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

#63 min, max, avg, median took s +0s ... 0.086s

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

#65 return log +0.004s ... 0.091s

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: Sebastian Jentsch,  8.09.2017 (Update: 19.05.2020)