Notebookcheck Logo

Apple S5 vs ARM Cortex-M4 vs Apple A6x

Apple S5

► remove from comparison Apple S5

Der Apple S5 ist ein 64-Bit-Prozessor mit zwei Kernen der in der Apple Watch Series 5 (40 und 44 mm) eingesetzt wird. Er integriert 32 GB Speicher, Bluetooth 5.0, 1 GB RAM, 802.11 b/g/n 2.4 GHz WLAN und Satelliten Positionierung (GPS, GLONASS, Galileo, QZSS).

Apple A6x

► remove from comparison

Der Apple A6x ist ein Zwei-Kern-SoC (System-on-a-Chip), mit ARM-kompatiblen Rechenkernen. Beim A6X handelt se sich wie beim wenigen Wochen zuvor vorgestellten A6-Chip um eine Eigenentwicklung von Apple, dessen Kerne sowohl den ARMv7-Befehlssatz als auch die erweiterte Version ARMv7s unterstützen. Die Strukturbreite beträgt 32 Nanometer. Die Taktfrequenz ist lastabhängig gesteuert und geht auf bis zu 1400 MHz hoch. 

Wie beim Vorgänger, dem A5X, deutet das X im Namen auf die gegenüber dem im iPhone 5 verbauten A6-Chip stärkere Grafikeinheit hin. Während die GPU des A6 mit drei Rechenkernen auskommen muss, verfügt der A6X über deren vier. Zudem verbaut Apple eine neue Version des Grafikchips aus dem Hause Imagination. Es handelt sich um den PowerVR SGX554MP4.

Zum Einsatz kommt der Apple A6X erstmals im iPad 4, das am 02. November 2012 auf den Markt kam. Im Verglich zum A5X-Chip aus dem iPad 3 sorgt der A6X etwa für  eine Verdopplung der Performance bei CPU und GPU.

ModelApple S5ARM Cortex-M4Apple A6x
SeriesApple Apple
Serie:
UNISOC Tiger T3101.8 - 2 GHz4 / 4
Rockchip RK32881.8 GHz4 / 4
Apple A6x1.4 GHz2
Apple A61 GHz2
» Apple S52 / 2
HiSilicon k3v2 Hi36201.2 GHz4 / 4
Rockchip RK3066 1.5 GHz1.5 GHz2 / 2
Amlogic AML8726-MX1.5 GHz2 / 2
Rockchip RK31681.2 GHz2 / 2
Rockchip RK2918 1.2 GHz1.2 GHz1 / 1
ARM Cortex A8 1.2 GHz1.2 GHz1 / 1
Telechips TCC8803 1GHz1 GHz1 / 1
Loongson 2F 900MHz0.9 GHz1 / 1
CSR86700.08 GHz2
ARM Cortex-M4
HiSilicon Hi6262
DK3.5+ST2
unknown
UNISOC Tiger T3101.8 - 2 GHz4 / 4
Rockchip RK32881.8 GHz4 / 4
Apple A6x1.4 GHz2
Apple A61 GHz2
Apple S52 / 2
HiSilicon k3v2 Hi36201.2 GHz4 / 4
Rockchip RK3066 1.5 GHz1.5 GHz2 / 2
Amlogic AML8726-MX1.5 GHz2 / 2
Rockchip RK31681.2 GHz2 / 2
Rockchip RK2918 1.2 GHz1.2 GHz1 / 1
ARM Cortex A8 1.2 GHz1.2 GHz1 / 1
Telechips TCC8803 1GHz1 GHz1 / 1
Loongson 2F 900MHz0.9 GHz1 / 1
CSR86700.08 GHz2
» ARM Cortex-M4
HiSilicon Hi6262
DK3.5+ST2
unknown
UNISOC Tiger T3101.8 - 2 GHz4 / 4
Rockchip RK32881.8 GHz4 / 4
» Apple A6x1.4 GHz2
Apple A61 GHz2
Apple S52 / 2
HiSilicon k3v2 Hi36201.2 GHz4 / 4
Rockchip RK3066 1.5 GHz1.5 GHz2 / 2
Amlogic AML8726-MX1.5 GHz2 / 2
Rockchip RK31681.2 GHz2 / 2
Rockchip RK2918 1.2 GHz1.2 GHz1 / 1
ARM Cortex A8 1.2 GHz1.2 GHz1 / 1
Telechips TCC8803 1GHz1 GHz1 / 1
Loongson 2F 900MHz0.9 GHz1 / 1
CSR86700.08 GHz2
ARM Cortex-M4
HiSilicon Hi6262
DK3.5+ST2
unknown
Cores / Threads2 / 22
Announced
Clock1400 MHz
Technology32 nm
ArchitectureARM

Benchmarks

3DMark - 3DMark Ice Storm Physics
100%
1 A6x +
8647 Points (6%)
3DMark - 3DMark Ice Storm Extreme Physics
100%
1 A6x +
8627 Points (7%)
3DMark - 3DMark Ice Storm Unlimited Physics
100%
1 A6x +
8850 Points (7%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
100%
1 A6x +
1424 Points (3%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
100%
1 A6x +
781 Points (15%)
Geekbench 2 - 32 Bit - Geekbench Stream
100%
1 A6x +
1012 Points (8%)
Geekbench 2 - 32 Bit - Geekbench Memory
100%
1 A6x +
2053 Points (19%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
100%
1 A6x +
2262 Points (4%)
Geekbench 2 - 32 Bit - Geekbench Integer
100%
1 A6x +
1330 Points (3%)
Geekbench 2 - 32 Bit - Geekbench Total Score
100%
1 A6x +
1768 Points (5%)
Linpack Android / IOS - Linpack Multi Thread
100%
1 A6x +
654 MFLOPS (22%)
Linpack Android / IOS - Linpack Single Thread
100%
1 A6x +
382.4 MFLOPS (37%)
Sunspider - Sunspider 1.0 Total Score *
100%
1 S5 +
min: 2014     avg: 2022     median: 2022 (22%)     max: 2030 ms
Sunspider - Sunspider 0.9.1 Total Score *
100%
1 A6x +
895 ms (8%)

Average Benchmarks Apple S5 → NAN% n=

Average Benchmarks Apple A6x → 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

v1.18
log 01. 23:25:25

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

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

#2 checking url part for id 3609 +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.005s

#6 linkCache_getLink no uid found +0.061s ... 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.066s

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

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

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

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

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

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

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

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

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

#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 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.067s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#53 getting avg benchmarks for device 11530 +0s ... 0.068s

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

#55 got single benchmarks 11530 +0.007s ... 0.075s

#56 getting avg benchmarks for device 13222 +0s ... 0.076s

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

#58 got single benchmarks 13222 +0.006s ... 0.082s

#59 getting avg benchmarks for device 3609 +0.001s ... 0.083s

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

#61 got single benchmarks 3609 +0.006s ... 0.089s

#62 got avg benchmarks for devices +0s ... 0.089s

#63 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.09s

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

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

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

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

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

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

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

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

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

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

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

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

#76 min, max, avg, median took s +0s ... 0.094s

#77 return log +0s ... 0.094s

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)