Notebookcheck Logo

Qualcomm Snapdragon S4 Pro MSM8960T vs Qualcomm Snapdragon 400 8930AB vs Qualcomm Snapdragon 400 APQ8028

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 8930AB

► remove from comparison Qualcomm 400 8930AB

Der Qualcomm Snapdragon 400 8930AB ist ein hoch getakteter ARM Dual-Core SoC für Android Smartphones. Er integriert zwei Krait 300 Kerne mit bis zu 1.7 GHz Taktfrequenz (MSM8930 hatte noch Krait 200 mit bis zu 1.2 GHz) und eine Adreno 305 Grafikkarte. Er wird im 28nm LP Verfahren gefertigt und bietet einen Single-channel-LPDDR2 Speicherkontroller (533 MHz).

Qualcomm Snapdragon 400 APQ8028

► remove from comparison Qualcomm 400 APQ8028

Der Qualcomm Snapdragon 400 APQ8028 ist ein preiswerter ARM-SoC für Android-Tablets. Er integriert vier Cortex-A7-Kerne mit bis zu 1,6 GHz Taktfrequenz und eine Adreno 305 Grafikkarte. Ein Funkmodem ist dagegen nicht enthalten.

Sowohl die Leistung des Prozessors auch die der Grafikeinheit ist nur im Einstiegssegment angesiedelt. Gemäß der Taktrate und der ähnlichen Pro-MHz-Leistung entspricht die Performance in etwa den schnelleren Varianten von Nvidias Tegra 3 oder dem Samsung Exynos 4412. Die Adreno 305 des APQ8028 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.

Durch den Verzicht auf ein Funkmodem ist der Chip in erster Linie für den Tablet-Einsatz geeignet. Dort unterstützt der SoC die Wiedergabe von 1080p-Videos und den Anschluss von USB-2.0-Geräten. Desweiteren können Kameras mit einer Auflösung von bis zu 13 Megapixeln angebunden werden.

Der SoC wird in einem 28nm LP Prozess gefertigt und sollte eine niedrige Leistungsaufnahme besitzen, sodass auch ein Einsatz in kleineren und dünnen Tablets möglich ist.

ModelQualcomm Snapdragon S4 Pro MSM8960TQualcomm Snapdragon 400 8930ABQualcomm Snapdragon 400 APQ8028
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
Clock1700 MHz1700 MHz1600 MHz
L1 Cache64 KB64 KB
L2 Cache1 MB1 MB
Cores / Threads2 / 22 / 24 / 4
Technology28 nm28 nm28 nm
FeaturesLTE, HSPA+, EDGE, GSM, GPRS, GPS, WiFi, Bluetooth, NFC, FMHSPA+, EDGE, GSM, GPRS, GPS, WiFi, Bluetooth, NFC, FMAdreno 305 GPU, LPDDR2/3 Memory Controller
iGPUQualcomm Adreno 320 (400 MHz)Qualcomm Adreno 305Qualcomm Adreno 305
ArchitectureARMARMARM
Announced
ManufacturerQualcomm Snapdragon 400 APQ8028

Benchmarks

3DMark - 3DMark Ice Storm Physics
7305 Points (5%)
min: 5181     avg: 6302     median: 6860 (4%)     max: 6864 Points
8132 Points (5%)
3DMark - 3DMark Ice Storm Extreme Physics
min: 7074     avg: 7129     median: 7129 (6%)     max: 7184 Points
min: 5397     avg: 6193     median: 6192.5 (5%)     max: 6988 Points
8177 Points (7%)
3DMark - 3DMark Ice Storm Unlimited Physics
8880 Points (7%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
min: 963     avg: 1098     median: 1098 (2%)     max: 1233 Points
1489 Points (3%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
min: 531     avg: 584     median: 583.5 (11%)     max: 636 Points
435 Points (8%)
Geekbench 2 - 32 Bit - Geekbench Stream
min: 632     avg: 668     median: 668 (5%)     max: 704 Points
min: 593     avg: 680     median: 716 (6%)     max: 731 Points
300 Points (2%)
Geekbench 2 - 32 Bit - Geekbench Memory
min: 2453     avg: 2630     median: 2630 (24%)     max: 2807 Points
min: 1527     avg: 1894     median: 2034 (18%)     max: 2121 Points
1334 Points (12%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
min: 2057     avg: 2521     median: 2520.5 (5%)     max: 2984 Points
min: 244     avg: 1983     median: 2853 (6%)     max: 2853 Points
2344 Points (5%)
Geekbench 2 - 32 Bit - Geekbench Integer
min: 871     avg: 1068     median: 1068 (2%)     max: 1265 Points
min: 898     avg: 1113     median: 1211 (2%)     max: 1229 Points
1369 Points (3%)
Geekbench 2 - 32 Bit - Geekbench Total Score
min: 1578     avg: 1848     median: 1848 (5%)     max: 2118 Points
min: 1394     avg: 1740     median: 1907 (5%)     max: 1919 Points
1596 Points (4%)
Linpack Android / IOS - Linpack Multi Thread
min: 225.8     avg: 246.4     median: 246.4 (8%)     max: 266.9 MFLOPS
min: 241.6     avg: 296     median: 298.5 (10%)     max: 347.8 MFLOPS
281 MFLOPS (10%)
Linpack Android / IOS - Linpack Single Thread
min: 166     avg: 169.5     median: 169.5 (17%)     max: 172.9 MFLOPS
min: 153.8     avg: 172.7     median: 171.1 (17%)     max: 193.2 MFLOPS
113 MFLOPS (11%)
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
min: 10213     avg: 13835     median: 13834.5 (16%)     max: 17456 ms
34416 ms (40%)
Sunspider - Sunspider 1.0 Total Score *
min: 1159     avg: 1422     median: 1421.5 (16%)     max: 1684 ms
min: 701     avg: 1047     median: 1117.5 (12%)     max: 1252 ms
958 ms (11%)
Sunspider - Sunspider 0.9.1 Total Score *
min: 1202     avg: 1329     median: 1250 (12%)     max: 1534 ms
min: 723     avg: 955     median: 954.5 (9%)     max: 1186 ms
Octane V2 - Octane V2 Total Score
min: 1466     avg: 2018     median: 2018 (2%)     max: 2570 Points
0 Points (0%)
1759 Points (2%)
Quadrant Standard Edition 2.0 - Quadrant Standard 2.0 Total Score
7510 points (17%)
6958 points (16%)
10657 points (25%)
AnTuTu v3 - AnTuTu v3 CPU
5727 Points (37%)
min: 4032     avg: 5115     median: 5644 (37%)     max: 5669 Points
AnTuTu v4 - AnTuTu v4 Total Score
17699 Points (41%)
18926 Points (44%)
AndEBench - AndEBench Java
min: 327     avg: 350     median: 350 (11%)     max: 373 Iter./s
min: 186     avg: 266     median: 266 (8%)     max: 346 Iter./s
400 Iter./s (12%)
AndEBench - AndEBench Native
min: 6665     avg: 6716     median: 6715.5 (22%)     max: 6766 Iter./s
min: 4389     avg: 4822     median: 4821.5 (16%)     max: 5254 Iter./s
8610 Iter./s (28%)
PassMark PerformanceTest Mobile V1 - PerformanceTest Mobile CPU Tests
7065 Points (1%)
min: 4329     avg: 6192     median: 7051 (1%)     max: 7195 Points
9698 Points (1%)

Average Benchmarks Qualcomm Snapdragon S4 Pro MSM8960T → 100% n=15

Average Benchmarks Qualcomm Snapdragon 400 8930AB → 91% n=15

Average Benchmarks Qualcomm Snapdragon 400 APQ8028 → 102% n=15

- 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 04. 19:35:25

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

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

#2 checking url part for id 6031 +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.006s ... 0.007s

#6 linkCache_getLink no uid found +0.004s ... 0.011s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#22 linkCache_getLink no uid found +0.004s ... 0.015s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#40 composed specs +0s ... 0.015s

#41 did output specs +0s ... 0.015s

#42 getting avg benchmarks for device 4455 +0s ... 0.015s

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

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

#45 got single benchmarks 4455 +0.009s ... 0.025s

#46 getting avg benchmarks for device 4413 +0.001s ... 0.025s

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

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

#49 got single benchmarks 4413 +0.009s ... 0.035s

#50 getting avg benchmarks for device 6031 +0.001s ... 0.036s

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

#52 got single benchmarks 6031 +0.006s ... 0.042s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#123 No cached benchmark found, getting uncached values +0s ... 0.056s

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

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

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

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

#128 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.058s

#129 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#130 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#131 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#132 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.058s

#133 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#134 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#135 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#136 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#137 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#138 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

#139 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

#140 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

#141 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

#142 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

#143 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

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

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

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

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

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

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

#150 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)