Notebookcheck Logo

Qualcomm Snapdragon S4 Plus MSM8930 vs Qualcomm Snapdragon 400 8930AB vs Qualcomm Snapdragon 400 APQ8028

Qualcomm Snapdragon S4 Plus MSM8930

► remove from comparison Qualcomm S4 Plus MSM8930

Der Qualcomm Snapdragon S4 Plus MSM8930 ist ein High-End-SoC für Smartphones und Tablets. Er besitzt einen ARM-basierten Dual-Core-Prozessor (mit 1-1.2 GHz) und entstammt der zweiten Generation der Snapdragon-Serie. Weiterhin integriert sind eine Adreno-305-GPU, ein Single-channel-LPDDR2-Speichercontroller sowie verschiedene Funkstandards jedoch inklusive LTE. Produziert wird der Chip von TSMC in einem 28-Nanometer-LP-Prozess.

Im Vergleich zu dem MSM8260A ist nur ein Single-Channel Speicherkontroller verbaut, dafür aber die schnellere Adreno 305 GPU.

Im Gegensatz zum Vorgängermodell, welches noch auf ältere Scorpion-Kerne setzte, kommt im MSM8930 die moderne Krait-Architektur zum Einsatz. Technisch ist diese etwas fortschrittlicher als der aktuelle Cortex-A9 vieler Mitbewerber. 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 typischerweise 1,5 bis 1,7 GHz sorgt in Verbindung mit einer stark verbesserten 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.

Im Multimediabereich kann der MSM8930 dank dedizierter Decoder-Einheiten mit der Wiedergabe von 1080p-Videos bis zu einer Framerate von 30 fps glänzen, 3D-Fotos sind bis zu einer Auflösung von 20 Megapixeln möglich.

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 Plus MSM8930Qualcomm 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
Clock1200 MHz1700 MHz1600 MHz
L1 Cache64 KB64 KB
L2 Cache1 MB1 MB
Cores / Threads2 / 22 / 24 / 4
Technology28 nm28 nm28 nm
FeaturesHSPA+, EDGE, GSM, GPRS, GPS, WiFi, Bluetooth, NFC, FMHSPA+, EDGE, GSM, GPRS, GPS, WiFi, Bluetooth, NFC, FMAdreno 305 GPU, LPDDR2/3 Memory Controller
iGPUQualcomm Adreno 305Qualcomm Adreno 305Qualcomm Adreno 305
ArchitectureARMARMARM
Announced
ManufacturerQualcomm Snapdragon 400 APQ8028

Benchmarks

3DMark - 3DMark Ice Storm Physics
min: 4629     avg: 4635     median: 4635 (3%)     max: 4641 Points
min: 5181     avg: 6302     median: 6860 (4%)     max: 6864 Points
8132 Points (5%)
3DMark - 3DMark Ice Storm Extreme Physics
4684 Points (4%)
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
788 Points (1%)
1489 Points (3%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
432 Points (9%)
435 Points (9%)
Geekbench 2 - 32 Bit - Geekbench Stream
min: 571     avg: 585     median: 584.5 (5%)     max: 598 Points
min: 593     avg: 680     median: 716 (6%)     max: 731 Points
300 Points (2%)
Geekbench 2 - 32 Bit - Geekbench Memory
min: 1449     avg: 1473     median: 1472.5 (13%)     max: 1496 Points
min: 1527     avg: 1894     median: 2034 (18%)     max: 2121 Points
1334 Points (12%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
min: 1778     avg: 1814     median: 1814 (4%)     max: 1850 Points
min: 244     avg: 1983     median: 2853 (6%)     max: 2853 Points
2344 Points (5%)
Geekbench 2 - 32 Bit - Geekbench Integer
min: 798     avg: 826     median: 825.5 (2%)     max: 853 Points
min: 898     avg: 1113     median: 1211 (2%)     max: 1229 Points
1369 Points (3%)
Geekbench 2 - 32 Bit - Geekbench Total Score
min: 1248     avg: 1277     median: 1276.5 (3%)     max: 1305 Points
min: 1394     avg: 1740     median: 1907 (5%)     max: 1919 Points
1596 Points (4%)
Linpack Android / IOS - Linpack Multi Thread
min: 146.9     avg: 205.6     median: 211.6 (7%)     max: 258.3 MFLOPS
min: 241.6     avg: 296     median: 298.5 (10%)     max: 347.8 MFLOPS
281 MFLOPS (10%)
Linpack Android / IOS - Linpack Single Thread
min: 25.25     avg: 106.5     median: 144.3 (14%)     max: 150 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 *
18650 ms (22%)
34416 ms (40%)
Sunspider - Sunspider 1.0 Total Score *
min: 1144     avg: 1189     median: 1189 (13%)     max: 1234 ms
min: 701     avg: 1047     median: 1117.5 (12%)     max: 1252 ms
958 ms (11%)
Sunspider - Sunspider 0.9.1 Total Score *
min: 1147     avg: 1282     median: 1224 (12%)     max: 1474 ms
min: 723     avg: 955     median: 954.5 (9%)     max: 1186 ms
Octane V2 - Octane V2 Total Score
0 Points (0%)
1759 Points (2%)
Quadrant Standard Edition 2.0 - Quadrant Standard 2.0 Total Score
min: 4557     avg: 4588     median: 4588 (11%)     max: 4619 points
6958 points (16%)
10657 points (25%)
AnTuTu v3 - AnTuTu v3 CPU
min: 3235     avg: 3312     median: 3311.5 (22%)     max: 3388 Points
min: 4032     avg: 5115     median: 5644 (37%)     max: 5669 Points
AnTuTu v4 - AnTuTu v4 Total Score
13681 Points (32%)
18926 Points (44%)
AndEBench - AndEBench Java
199 Iter./s (6%)
min: 186     avg: 266     median: 266 (8%)     max: 346 Iter./s
400 Iter./s (12%)
AndEBench - AndEBench Native
4569 Iter./s (15%)
min: 4389     avg: 4822     median: 4821.5 (16%)     max: 5254 Iter./s
8610 Iter./s (28%)
PassMark PerformanceTest Mobile V1 - PerformanceTest Mobile CPU Tests
3464 Points (0%)
min: 4329     avg: 6192     median: 7051 (1%)     max: 7195 Points
9698 Points (1%)

Average Benchmarks Qualcomm Snapdragon S4 Plus MSM8930 → 100% n=14

Average Benchmarks Qualcomm Snapdragon 400 8930AB → 139% n=14

Average Benchmarks Qualcomm Snapdragon 400 APQ8028 → 152% n=14

- 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. 17:26:30

#0 checking url part for id 3725 +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 Sat, 02 Jul 2022 13:13:02 +0200 +0s ... 0s

#5 linkCache_getLink no uid found +0.005s ... 0.006s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#23 linkCache_getLink no uid found +0.003s ... 0.012s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#41 composed specs +0s ... 0.012s

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

#43 getting avg benchmarks for device 3725 +0s ... 0.013s

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

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

#46 got single benchmarks 3725 +0.01s ... 0.023s

#47 getting avg benchmarks for device 4413 +0s ... 0.024s

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

#49 got single benchmarks 4413 +0.007s ... 0.031s

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

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

#52 got single benchmarks 6031 +0.005s ... 0.037s

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

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

#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.043s

#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.043s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#92 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.046s

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

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

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

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

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

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

#99 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.047s

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

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

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

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

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

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

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

#107 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.049s

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

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

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

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

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

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

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

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

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

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

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

#119 No cached benchmark found, getting uncached values +0s ... 0.051s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#136 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.055s

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

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

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

#140 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.056s

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

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

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

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

#145 min, max, avg, median took s +0s ... 0.057s

#146 return log +0s ... 0.057s

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)