Notebookcheck Logo

Qualcomm Snapdragon S4 Plus APQ8060A vs Qualcomm Snapdragon S4 Pro APQ8064A

Qualcomm Snapdragon S4 Plus APQ8060A

► remove from comparison Qualcomm S4 Plus APQ8060A

Der Qualcomm Snapdragon S4 Plus APQ8060 ist ein High-End-SoC für Smartphones und Tablets. Er besitzt einen ARM-basierten Dual-Core-Prozessor und entstammt der zweiten Generation der Snapdragon-Serie. Weiterhin integriert sind eine Adreno-225-GPU, ein LPDDR2-Speichercontroller. Im Vergleich zum MSM8260A fehlt ihm jedoch das Funkmodul für GSM, GPRS, UMTS und LTE. Produziert wird der Chip von TSMC in einem 28-Nanometer-LP-Prozess.

Im Gegensatz zum Vorgängermodell, welches noch auf ältere Scorpion-Kerne setzte, kommt im 8060A 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.

Die Adreno-225-Grafikeinheit (für WUXGA/1080p lt Qualcomm) ist im Wesentlichen eine schnellere Version der DirectX-9-fähigen Adreno 220 im APQ8060A. Statt mit 266 MHz taktet die GPU nun 50 Prozent höher auf 400 MHz, was zusammen mit der drastisch gesteigerten Speicherbandbreite (Dual-Channel-LPDDR2 bis 500 MHz) für einen spürbaren Leistungssprung sorgen sollte. Erste Benchmarks deuten an, dass auch die starke PowerVR SGX 543MP2 von Apples A5-SoC übertroffen wird.

Im Multimediabereich kann der 8060A 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.

Die Leistungsaufnahme soll dank des kleineren Prozesses unterhalb des Vorgängers liegen, wobei Qualcomm keine genaueren Angaben zur verwendeten Anwendung macht. In der Praxis kann, je nach Auslastung, vermutlich mit leicht verbesserten Akkulaufzeiten gerechnet werden.

Qualcomm Snapdragon S4 Pro APQ8064A

► remove from comparison Qualcomm S4 Pro APQ8064A

Der Qualcomm Snapdragon S4 Pro APQ8064A ist ein High-End-SoC für Android-Smartphones und -Tablets, der im Jahr 2012 vorgestellt wurde. Der Chip integriert 4 CPU-Kerne, welche auf der ARMv7-kompatiblen, von Qualcomm aber selbst entwickelten Krait-Architektur basieren. Diese bietet eine deutlich höhere Pro-MHz-Leistung als Cortex-A9-Chips wie Nvidias Tegra 3 oder der Exynos 4412 von Samsung, kommt aber nicht ganz an die Performance des Cortex-A15 heran (beispielsweise im Tegra 4). Der Speicherzugriff erfolgt über 2x 32 Bit LPDDR2 mit maximal 533 MHz Takt, was einer Bandbreite von 8,5 GB/s entspricht.

Der APQ8064A verfügt über eine Adreno-320-GPU von IMG, welche bei einer Taktrate von 400 MHz eine Rechenleistung von gut 50 GFLOPS erzielt. Damit zählt die Grafikeinheit zu den derzeit (Anfang 2013) schnellsten im SoC-Bereich und wird nur von wenigen Modellen wie beispielsweise der PowerVR SGX554MP4 im iPad 4 übertroffen. Auch grafisch aufwändige Spiele können so in FullHD-Auflösung (wie beispielsweise beim Sony Xperia Z) flüssig dargestellt werden.

Im Multimediabereich kann der APQ8064A 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. Zudem integriert der Chip auch ein Funkmodul mit Bluetooth 4.0 und WLAN nach 802.11ac/a/b/g/n. Die Leistungsaufnahme des von TSMC in 28 Nanometer (LP) produzierten Chips sollte je nach Taktrate bei maximal 4 Watt liegen (Schätzung).

ModelQualcomm Snapdragon S4 Plus APQ8060AQualcomm Snapdragon S4 Pro APQ8064A
SeriesQualcomm SnapdragonQualcomm Snapdragon
CodenameARMv7ARMv7
Serie: Snapdragon ARMv7
Qualcomm Snapdragon S4 Pro APQ8064A1.5 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM8928 compare1.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ8028 compare1.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Pro MSM8960T compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 8930AB compare1.7 GHz2 / 2 ARMv7
» Qualcomm Snapdragon S4 Plus APQ8060A1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8960 compare1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8260A compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 MSM8926 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM8226 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ8026 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Plus MSM8930 compare1.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8230 compare1.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8227 compare1 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM8660 compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM8260 compare1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S1 QSD8250 compare1 GHz1 / 1 ARMv7
» Qualcomm Snapdragon S4 Pro APQ8064A1.5 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM8928 compare1.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ8028 compare1.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Pro MSM8960T compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 8930AB compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus APQ8060A1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8960 compare1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8260A compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 MSM8926 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM8226 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ8026 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Plus MSM8930 compare1.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8230 compare1.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8227 compare1 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM8660 compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM8260 compare1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S1 QSD8250 compare1 GHz1 / 1 ARMv7
Clock1500 MHz1500 - 1700 MHz
L1 Cache64 KB32 KB
L2 Cache1 MB2 MB
Cores / Threads2 / 24 / 4
Technology28 nm28 nm
iGPUQualcomm Adreno 225 (266 MHz)Qualcomm Adreno 320 (400 MHz)
ArchitectureARMARM
Announced
FeaturesLTE, HSPA+, EDGE, GSM, GPRS, GPS, WiFi, Bluetooth, NFC, FM

Benchmarks

3DMark - 3DMark Ice Storm Physics
5324 Points (3%)
3DMark - 3DMark Ice Storm Extreme Physics
5422 Points (4%)
3DMark - 3DMark Ice Storm Unlimited Physics
5570 Points (5%)
11099 Points (9%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
min: 1304     avg: 1473     median: 1473 (3%)     max: 1642 Points
Geekbench 3 - Geekbench 3 32 Bit Single-Core
min: 485     avg: 498     median: 498 (10%)     max: 511 Points
Geekbench 2 - 32 Bit - Geekbench Stream
624 Points (5%)
Geekbench 2 - 32 Bit - Geekbench Memory
1677 Points (15%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
2109 Points (4%)
Geekbench 2 - 32 Bit - Geekbench Integer
963 Points (2%)
Geekbench 2 - 32 Bit - Geekbench Total Score
1473 Points (4%)
Linpack Android / IOS - Linpack Multi Thread
181.8 MFLOPS (6%)
Linpack Android / IOS - Linpack Single Thread
103.9 MFLOPS (10%)
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
43092 ms (50%)
min: 14529     avg: 14855     median: 14854.5 (17%)     max: 15180 ms
Sunspider - Sunspider 0.9.1 Total Score *
min: 942     avg: 1297     median: 997 (9%)     max: 1951 ms
Sunspider - Sunspider 1.0 Total Score *
min: 854     avg: 1378     median: 1337 (15%)     max: 2012 ms
Octane V2 - Octane V2 Total Score
2223 Points (2%)
Vellamo 3.x - Vellamo 3.x Metal
723 Points (19%)
Vellamo 3.x - Vellamo 3.x Multicore Beta
1230 Points (27%)
Vellamo 3.x - Vellamo 3.x Browser
1580 Points (21%)
Quadrant Standard Edition 2.0 - Quadrant Standard 2.0 Total Score
5015 points (12%)
AnTuTu v3 - AnTuTu v3 CPU
min: 6086     avg: 7440     median: 7290 (47%)     max: 8596 Points
AnTuTu v4 - AnTuTu v4 Total Score
20270 Points (47%)
AnTuTu v5 - AnTuTu v5 Total Score
25095 Points (25%)
AndEBench - AndEBench Java
min: 144     avg: 321.5     median: 345 (11%)     max: 452 Iter./s
AndEBench - AndEBench Native
min: 8393     avg: 9636     median: 9432.5 (31%)     max: 11286 Iter./s
PassMark PerformanceTest Mobile V1 - PerformanceTest Mobile CPU Tests
min: 8536     avg: 10282     median: 10517.5 (1%)     max: 11558 Points
PCMark for Android - PCM f. Android Work Score
2735 Points (14%)

Average Benchmarks Qualcomm Snapdragon S4 Plus APQ8060A → 100% n=13

Average Benchmarks Qualcomm Snapdragon S4 Pro APQ8064A → 161% n=13

- 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

Add one or more devices and compare

In the following list you can select (and also search for) devices that should be added to the comparison. You can select more than one device.

restrict list:

show all (including archived), 2022, 2021
v1.17
log 13. 03:43:38

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

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

#2 not redirecting to Ajax server +0s ... 0s

#3 did not recreate cache, as it is less than 5 days old! Created at Thu, 11 Aug 2022 13:13:36 +0200 +0s ... 0s

#4 linkCache_getLink no uid found +0.004s ... 0.005s

#5 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.006s

#6 linkCache_getLink no uid found +0.006s ... 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 using $NBC_LINKCACHE +0s ... 0.011s

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

#24 did output specs +0s ... 0.012s

#25 getting avg benchmarks for device 3588 +0s ... 0.012s

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

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

#28 got single benchmarks 3588 +0.007s ... 0.019s

#29 getting avg benchmarks for device 3645 +0.001s ... 0.02s

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

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

#32 got single benchmarks 3645 +0.014s ... 0.035s

#33 got avg benchmarks for devices +0s ... 0.035s

#34 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.036s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#171 linkCache_getLink no uid found +0s ... 0.049s

#172 min, max, avg, median took s +0s ... 0.05s

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

#174 return log +0.004s ... 0.054s

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)