Notebookcheck Logo

Qualcomm Snapdragon S3 MSM8260 vs Qualcomm Snapdragon S4 Pro MSM8960T vs Qualcomm Snapdragon 400 APQ8026

Qualcomm Snapdragon S3 MSM8260

► remove from comparison Qualcomm S3 MSM8260

Der Qualcomm Snapdragon S3 MSM8260 ist ein Einstiegs-SoC für Smartphones und Tablets. Er besitzt einen ARM-basierten Dual-Core-Prozessor und entstammt der ersten Generation der Snapdragon-Serie. Die CPU Kerne basieren auf der alten Scorpion Architektur (verbesserte Cortex-A8 Architektur). Weiters ist eine Adreno 220 Grafikkarte integriert.

Qualcomm Snapdragon S4 Pro MSM8960T

► remove from comparison Qualcomm MSM8960T

Der Qualcomm MSM8960T (Modellreihe Snapdragon S4 Pro) ist ein schneller ARM-SoC, der vorrangig in Smartphones eingesetzt wird. Er besitzt einen Krait-basierten Dual-Core-Prozessor sowie eine Adreno-320-Grafikeinheit. Weiterhin integriert sind ein LPDDR2-Speichercontroller (Dual-Channel, max. 500 MHz) sowie verschiedene Funkstandards inklusive LTE. Gefertigt wird der Chip von TSMC in einem 28-Nanometer-LP-Prozess.

Im Gegensatz zu älteren Qualcomm-SoCs, welche noch auf langsameren Scorpion-Kernen basierten, kommt im MSM8960T die moderne Krait-Architektur zum Einsatz. Diese ist deutlich schneller als die Cortex-A5-, Cortex-A7- und Cortex-A9-Architektur von ARM und liegt nur knapp hinter dem High-End-Design Cortex-A15. Beiden Kernen steht ein jeweils 32 KB großer L1-Cache sowie ein gemeinsamer L2-Cache mit 1 MB Kapazität zur Verfügung. Eine hohe Taktrate von bis zu 1,7 GHz sorgt in Verbindung mit der hohen Pro-MHz-Leistung dafür, dass die Performance noch über dem Niveau eines Quad-Core Cortex-A9 wie beispielsweise Nvidias Tegra 3 liegt. Auch die NEON-Befehlssatzerweiterung für bis zu 128 Bit breite Operanden wird unterstützt.

Die Adreno-320-Grafikeinheit kommt auch im Snapdragon 600 zum Einsatz und zählt Mitte 2013 zu den schnellsten Mobile-GPUs überhaupt. Der typischerweise mit 400 MHz taktende Chip besitzt genügend Reserven, um auch hochauflösende FullHD-Displays und aufwändige Spiele zu bewältigen.

Da der MSM8960T nur über zwei CPU-Kerne verfügt, sollte die Leistungsaufnahme etwas unterhalb von Quad-Core-SoCs wie dem Snapdragon 600 liegen. Der Chip kann deshalb auch in kleineren Smartphones mit schwächerem Akku eingesetzt werden können.

Qualcomm Snapdragon 400 APQ8026

► remove from comparison Qualcomm 400 APQ8026

Der Qualcomm Snapdragon 400 APQ8026 ist ein preiswerter ARM-SoC für Android-Smartphones. Er integriert vier Cortex-A7-Kerne mit bis zu 1.2 GHz Taktfrequenz, eine 450 MHz schnelle Adreno 305 Grafikkarte sowie einen Single-Channel LPDDR2/3-1066 Speichercontroller.

Sowohl die Leistung des Prozessors auch die der Grafikeinheit ist nur im Einstiegssegment angesiedelt. Ähnlich hoch taktende Cortex-A7-Kerne bietet zum Beispiel auch der Mediatek MT6589, der allerdings eine etwas schwächere PowerVR-GPU integriert. Die Adreno 305 des MSM8226 besitzt für Multimedia-Zwecke und einfache Android-Spiele ausreichende Leistungsreserven, ist jedoch nicht für anspruchsvolle 3D-Grafiken und extrem hohe Auflösungen geeignet.

Neben Prozessor und Grafikkarte integriert der Chip auch Bluetooth 4.0. Desweiteren können Kameras mit einer Auflösung von bis zu 13 Megapixeln angebunden werden. Zu den unterstützten Video-Codecs zählen unter anderem H.264 und H.265 (nur Wiedergabe) bis zu einer Auflösung von 1080p.

Der APQ8026 wird in einem 28nm LP Prozess gefertigt und besitzt eine sehr niedrige Leistungsaufnahme, sodass auch ein Einsatz in kompakten Smartphones oder gar Smartwatches möglich ist.

ModelQualcomm Snapdragon S3 MSM8260Qualcomm Snapdragon S4 Pro MSM8960TQualcomm Snapdragon 400 APQ8026
SeriesQualcomm SnapdragonQualcomm SnapdragonQualcomm Snapdragon
CodenameARMv7ARMv7ARMv7
Serie: Snapdragon ARMv7
Qualcomm Snapdragon S4 Pro APQ8064A1.5 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM89281.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ80281.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Pro MSM8960T1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 8930AB1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus APQ8060A1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM89601.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8260A1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 MSM89261.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM82261.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ80261.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Plus MSM89301.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM82301.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM82271 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM86601.7 GHz2 / 2 ARMv7
» Qualcomm Snapdragon S3 MSM82601.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S1 QSD82501 GHz1 / 1 ARMv7
Qualcomm Snapdragon S4 Pro APQ8064A1.5 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM89281.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ80281.6 GHz4 / 4 ARMv7
» Qualcomm Snapdragon S4 Pro MSM8960T1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 8930AB1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus APQ8060A1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM89601.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8260A1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 MSM89261.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM82261.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ80261.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Plus MSM89301.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM82301.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM82271 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM86601.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM82601.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S1 QSD82501 GHz1 / 1 ARMv7
Qualcomm Snapdragon S4 Pro APQ8064A1.5 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM89281.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ80281.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Pro MSM8960T1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 8930AB1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus APQ8060A1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM89601.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8260A1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 MSM89261.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM82261.2 GHz4 / 4 ARMv7
» Qualcomm Snapdragon 400 APQ80261.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Plus MSM89301.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM82301.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM82271 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM86601.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM82601.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S1 QSD82501 GHz1 / 1 ARMv7
Clock1500 MHz1700 MHz1200 MHz
L1 Cache64 KB64 KB
L2 Cache1 MB1 MB
Cores / Threads2 / 22 / 24 / 4
Technology45 nm28 nm28 nm
FeaturesHSPA+, EDGE, GSM, GPRS, GPS, WiFi, Bluetooth, NFC, FMLTE, HSPA+, EDGE, GSM, GPRS, GPS, WiFi, Bluetooth, NFC, FMBluetooth 4.0
iGPUQualcomm Adreno 220Qualcomm Adreno 320 (400 MHz)Qualcomm Adreno 305 (450 MHz)
ArchitectureARMARMARM
Announced
ManufacturerQualcomm Snapdragon 400 APQ8026

Benchmarks

3DMark - 3DMark Ice Storm Physics
7305 Points (5%)
6749 Points (4%)
3DMark - 3DMark Ice Storm Extreme Physics
min: 7074     avg: 7129     median: 7129 (6%)     max: 7184 Points
6667 Points (6%)
3DMark - 3DMark Ice Storm Unlimited Physics
7226 Points (6%)
Geekbench 2 - 32 Bit - Geekbench Stream
385 Points (3%)
min: 632     avg: 668     median: 668 (5%)     max: 704 Points
272 Points (2%)
Geekbench 2 - 32 Bit - Geekbench Memory
1034 Points (9%)
min: 2453     avg: 2630     median: 2630 (24%)     max: 2807 Points
1192 Points (11%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
1230 Points (2%)
min: 2057     avg: 2521     median: 2520.5 (5%)     max: 2984 Points
1803 Points (4%)
Geekbench 2 - 32 Bit - Geekbench Integer
912 Points (2%)
min: 871     avg: 1068     median: 1068 (2%)     max: 1265 Points
1093 Points (2%)
Geekbench 2 - 32 Bit - Geekbench Total Score
994 Points (3%)
min: 1578     avg: 1848     median: 1848 (5%)     max: 2118 Points
1279 Points (3%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
min: 963     avg: 1098     median: 1098 (2%)     max: 1233 Points
1075 Points (2%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
min: 531     avg: 584     median: 583.5 (12%)     max: 636 Points
327 Points (7%)
Linpack Android / IOS - Linpack Multi Thread
76.5 MFLOPS (3%)
min: 225.8     avg: 246.4     median: 246.4 (8%)     max: 266.9 MFLOPS
242.3 MFLOPS (8%)
Linpack Android / IOS - Linpack Single Thread
43.2 MFLOPS (4%)
min: 166     avg: 169.5     median: 169.5 (17%)     max: 172.9 MFLOPS
85.2 MFLOPS (8%)
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
min: 10213     avg: 13835     median: 13834.5 (16%)     max: 17456 ms
16134 ms (19%)
Sunspider - Sunspider 0.9.1 Total Score *
1888 ms (18%)
min: 1202     avg: 1329     median: 1250 (12%)     max: 1534 ms
1157 ms (11%)
Sunspider - Sunspider 1.0 Total Score *
min: 1159     avg: 1422     median: 1421.5 (16%)     max: 1684 ms
1137 ms (12%)
Octane V2 - Octane V2 Total Score
min: 1466     avg: 2018     median: 2018 (2%)     max: 2570 Points
1810 Points (2%)
Vellamo 3.x - Vellamo 3.x Metal
755 Points (20%)
Vellamo 3.x - Vellamo 3.x Multicore Beta
1152 Points (26%)
Vellamo 3.x - Vellamo 3.x Browser
1546 Points (20%)
Quadrant Standard Edition 2.0 - Quadrant Standard 2.0 Total Score
7510 points (17%)
8236 points (19%)
AnTuTu v3 - AnTuTu v3 CPU
3197 Points (21%)
5727 Points (37%)
AnTuTu v4 - AnTuTu v4 Total Score
17699 Points (41%)
17735 Points (41%)
AnTuTu v5 - AnTuTu v5 Total Score
17247 Points (17%)
AndEBench - AndEBench Java
min: 327     avg: 350     median: 350 (11%)     max: 373 Iter./s
308 Iter./s (9%)
AndEBench - AndEBench Native
min: 6665     avg: 6716     median: 6715.5 (22%)     max: 6766 Iter./s
6098 Iter./s (20%)
PassMark PerformanceTest Mobile V1 - PerformanceTest Mobile CPU Tests
7065 Points (1%)
6717 Points (1%)

Average Benchmarks Qualcomm Snapdragon S3 MSM8260 → 100% n=8

Average Benchmarks Qualcomm Snapdragon S4 Pro MSM8960T → 220% n=8

Average Benchmarks Qualcomm Snapdragon 400 APQ8026 → 150% 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 05. 09:29:57

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

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

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

#6 linkCache_getLink no uid found +0.006s ... 0.01s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#22 linkCache_getLink no uid found +0.003s ... 0.013s

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

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

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

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

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

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

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

#30 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.013s

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

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

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

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

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

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

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

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

#39 composed specs +0s ... 0.013s

#40 did output specs +0s ... 0.013s

#41 getting avg benchmarks for device 3760 +0s ... 0.014s

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

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

#44 got single benchmarks 3760 +0.006s ... 0.02s

#45 getting avg benchmarks for device 4455 +0.001s ... 0.021s

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

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

#48 got single benchmarks 4455 +0.007s ... 0.029s

#49 getting avg benchmarks for device 6436 +0s ... 0.029s

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

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

#52 got single benchmarks 6436 +0.007s ... 0.037s

#53 got avg benchmarks for devices +0s ... 0.037s

#54 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.039s

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

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

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

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

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

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

#61 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#78 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

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

#80 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#81 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

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

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

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

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

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

#87 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.046s

#88 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.046s

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

#90 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.047s

#91 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.047s

#92 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.047s

#93 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#94 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#95 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#96 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#97 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#98 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#99 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#100 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.049s

#101 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.049s

#102 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.049s

#103 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.05s

#104 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#105 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#106 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.051s

#107 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.051s

#108 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.052s

#109 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.052s

#110 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.052s

#111 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#112 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#113 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#114 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.053s

#115 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.054s

#116 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.054s

#117 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.054s

#118 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.054s

#119 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.054s

#120 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.055s

#121 min, max, avg, median took s +0s ... 0.055s

#122 return log +0s ... 0.055s

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)