Notebookcheck Logo

Apple S5 vs ARM Cortex-M4 vs DK3.5+ST

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

ModelApple S5ARM Cortex-M4DK3.5+ST
SeriesApple Huawei
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

Benchmarks

Sunspider - Sunspider 1.0 Total Score *
100%
1 S5 +
min: 2014     avg: 2022     median: 2022 (22%)     max: 2030 ms

Average Benchmarks Apple S5 → 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. 22:32:43

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

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

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

#6 linkCache_getLink no uid found +0.038s ... 0.042s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#39 linkCache_getLink no uid found +0s ... 0.043s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#55 got single benchmarks 11530 +0.006s ... 0.05s

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

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

#58 got single benchmarks 13222 +0.005s ... 0.055s

#59 getting avg benchmarks for device 12765 +0s ... 0.055s

#60 linkCache_getLink no uid found +0s ... 0.055s

#61 got single benchmarks 12765 +0.005s ... 0.061s

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

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

#64 min, max, avg, median took s +0s ... 0.061s

#65 return log +0s ... 0.061s

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)