, , , , , ,
zu verknüpfen.
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
 

NVIDIA Quadro 5000M vs NVIDIA Quadro M600M

NVIDIA Quadro 5000M

► remove from comparison NVIDIA Quadro 5000M

Die NVIDIA Quadro 5000M ist eine auf die Fermi Architektur basierende professionelle Workstation Grafikkarte für Notebooks. Sie basiert wahrscheinlich auf die selbe Architektur wie die Consumer GeForce GTX 480M, bietet jedoch nur 320 Shader (hier genannt CUDA Cores). Sie ist die erste mobile GPU, welche sowohl ECC als auch Double-Precision-Gleitkommaberechnungen bietet.

Die Quadro Grafikkarten bieten zertifizierte Treiber, welche auf Stabiltität und Performance bei professionellen Anwendungen (CAD-, DCC-, Medizin-, Prospektions-, Visualisierungsanwendungen) optimiert sind. Dadurch ist die Performance im Vergleich zu den Consumergrafikkarten mit gleichem Chip deutlich besser in diesen Bereichen.

Die Recheneinheiten der Quadro5000M können durch die Schnittstellen DirectX 11, OpenGL 4.1, DirectCompute, OpenCL, AXE und CUDA angesprochen werden und auch für generelle Aufgaben genutzt werden (nicht nur die Grafikberechnung). Die Fermi Architektur soll außerdem im Insbesonderen auf diese generellen Berechnungen optimiert worden sein, wordurch man eine hohe Performance erwarten kann.

Durch den Einsatz von schnellem GDDR5 Grafikspeicher, sollte der 256 Bit Speicherbus nicht zum Flaschenhals der Grafikkarte werden und kann bis zu 76.8 GB / Sekunde übertragen.

Die Nvidia Quadro 5000M ist kompatibel mit der Steroscopic-Lösung NVIDIA 3D Vision Pro.

Wie auch die GeForce GTX 480M, ist die Quadro 5000M mit 100 Watt TDP spezifiziert  und eignet sich daher nur für sehr große und schwere Notebooks (wie das Clevo D901F Barebone).

Die Quadro 5000M ist zum Zeitpunkt des Erscheinens (Mitte 2010) die schnellste Profi-Grafikkarte für Notebooks und löst die Quadro FX 3800M bei Nvidia ab. Anfang 2011 wurde sie von der Quadro 5010M mit abgelöst. Verglichen zu Desktop Grafikkarten, wird die Desktop Quadro 5000 wahrscheinlich schneller getaktet sein und bietet auch mehr CUDA Cores (352). 

NVIDIA Quadro M600M

► remove from comparison NVIDIA Quadro M600M

Die NVIDIA Quadro M600M ist eine DirectX-12 (FL 11_0) und OpenGL-4.5 fähige Einstiegs-Workstation-Grafikkarte für Notebooks. Sie basiert wie die Consumer GeForce GTX 950M auf den GM108-Chip der Maxwell-Serie und wird in 28nm bei TSMC hergestellt. Wie bei der GM107 basierenden Quadro K620M / GeForce 940M sind jedoch nur 384 Shader aktiv, trotzdem bietet die M600M einen 128 Bit Speicherbus. Die Grafikkarte ist für die Skylake-Generation gedacht. Es werden bis zu 4 GB GDDR5 als Grafikspeicher eingesetzt die mit 1.250 MHz (5.000 MHz effektiv) getaktet werden und über einen 128 Bit Speicherbus angebunden sind (80 vs 16 GB/s bei der K620M).

Im Lenovo Thinkpad P70 arbeitet die M600M mit 837 - 876 MHz (Boost) und einem Speichertakt von 1253 MHz (5012 MHz effektiv).

Die Quadro-Grafikkarten bieten zertifizierte Treiber, welche auf Stabiltität und Performance bei professionellen Anwendungen (CAD-, DCC-, Medizin-, Prospektions-, Visualisierungsanwendungen) optimiert sind. Dadurch ist die Performance im Vergleich zu den Consumergrafikkarten mit gleichem Chip in diesen Bereichen deutlich besser.

Leistung

Dank dem 128 Bit großen Speicherbus liegt die Quadro M600M etwa 20 Prozent vor der alten Quadro K620M positionieren und ziemlich genau zwischen den Geschwistern Quadro M500M & Quadro M1000M. Im Consumerbereich wird die GeForce 940MX um etwa 10-15 % überholt, während die GeForce GTX 950M ihrerseits bis zu 20 % schneller arbeitet.

Die Rechenkerne der Grafikkarte können per CUDA und OpenCL 1.2 auch für generelle Berechnungen herangezogen werden.

Leistungsaufnahme

Die Leistungsaufnahme der Quadro M600M entspricht laut Nvidia der alten Quadro K620M und liegt bei 30 Watt TGP (Max Power Consumption). Dadurch ist die Karte auch für dünne und leichte Notebooks geeignet.

NVIDIA Quadro 5000MNVIDIA Quadro M600M
HerstellerNVIDIANVIDIA
Quadro M Serie
Quadro M5500 compare 2048 @ 1.14 - 1.14 GHz256 Bit @ 6606 MHz
Quadro M5000M compare 1536 @ 0.96 - 1.05 GHz256 Bit @ 5000 MHz
Quadro M4000M compare 1280 @ 0.98 - 1.01 GHz256 Bit @ 5012 MHz
Quadro M3000M compare 1024 @ 1.05 GHz256 Bit @ 5000 MHz
Quadro M2200 compare 1024 @ 0.69 - 1.04 GHz128 Bit @ 5508 MHz
Quadro M1200 compare 640 @ 0.99 - 1.15 GHz128 Bit @ 5000 MHz
Quadro M2000M compare 640 @ 1.04 - 1.2 GHz128 Bit @ 5000 MHz
Quadro M1000M compare 512 @ 0.99 - 1.07 GHz128 Bit @ 5000 MHz
Quadro M620 compare 512 @ 1.02 GHz128 Bit @ 5012 MHz
Quadro 5010M compare 384 @ 0.45 GHz256 Bit @ 1300 MHz
Quadro 4000M compare 336 @ 0.48 GHz256 Bit @ 1200 MHz
Quadro M520 compare 384 @ 0.76 - 1.02 GHz64 Bit
Quadro M600M 384 @ 0.84 - 0.88 GHz128 Bit @ 5012 MHz
Quadro M500M compare 384 @ 1.03 - 1.12 GHz64 Bit @ 4004 MHz
Quadro 5000M 320 @ 0.41 GHz256 Bit @ 1200 MHz
Quadro 3000M compare 240 @ 0.45 GHz256 Bit @ 625 MHz
Quadro 2000M compare 192 @ 0.55 GHz128 Bit @ 900 MHz
Quadro 1000M compare 96 @ 0.7 GHz128 Bit @ 900 MHz
Quadro M5500 compare 2048 @ 1.14 - 1.14 GHz256 Bit @ 6606 MHz
Quadro M5000M compare 1536 @ 0.96 - 1.05 GHz256 Bit @ 5000 MHz
Quadro M4000M compare 1280 @ 0.98 - 1.01 GHz256 Bit @ 5012 MHz
Quadro M3000M compare 1024 @ 1.05 GHz256 Bit @ 5000 MHz
Quadro M2200 compare 1024 @ 0.69 - 1.04 GHz128 Bit @ 5508 MHz
Quadro M1200 compare 640 @ 0.99 - 1.15 GHz128 Bit @ 5000 MHz
Quadro M2000M compare 640 @ 1.04 - 1.2 GHz128 Bit @ 5000 MHz
Quadro M1000M compare 512 @ 0.99 - 1.07 GHz128 Bit @ 5000 MHz
Quadro M620 compare 512 @ 1.02 GHz128 Bit @ 5012 MHz
Quadro 5010M compare 384 @ 0.45 GHz256 Bit @ 1300 MHz
Quadro 4000M compare 336 @ 0.48 GHz256 Bit @ 1200 MHz
Quadro M520 compare 384 @ 0.76 - 1.02 GHz64 Bit
Quadro M600M 384 @ 0.84 - 0.88 GHz128 Bit @ 5012 MHz
Quadro M500M compare 384 @ 1.03 - 1.12 GHz64 Bit @ 4004 MHz
Quadro 5000M 320 @ 0.41 GHz256 Bit @ 1200 MHz
Quadro 3000M compare 240 @ 0.45 GHz256 Bit @ 625 MHz
Quadro 2000M compare 192 @ 0.55 GHz128 Bit @ 900 MHz
Quadro 1000M compare 96 @ 0.7 GHz128 Bit @ 900 MHz
CodenameFermi
ArchitekturFermiMaxwell
Pipelines320 - unified384 - unified
Kerntakt405 MHz837 - 876 (Boost) MHz
Shadertakt810 MHz
Speichertakt1200 MHz5012 MHz
Speicherbandbreite256 Bit128 Bit
SpeichertypGDDR5GDDR5
Max. Speichergröße2048 MB2048 MB
Shared Memoryneinnein
DirectXDirectX 11, Shader 5.0DirectX 12 (FL 11_0), Shader 5.0
Transistors3000 Million
Herstellungsprozess40 nm28 nm
FeaturesOpenGL 4.1, DirectX 11, DirectCompute, OpenCL, CUDA, AXE, Error-Correction-Codes (ECC)-Memory, IEEE-Double-Precision-Floating-Point, PowerMizer 9.0Optimus, PhysX, 3D Vision Pro, nView, Optimus
Notebookgrößegroß (17" z.B.)groß (17" z.B.)
Erscheinungsdatum27.07.2010 02.10.2015
Herstellerseitehttp://www.nvidia.com/object/product-qua...http://www.nvidia.com/object/quadro-for-...

Benchmarks

Performance Rating - 3DMark 11 + Fire Strike + Time Spy - Quadro M600M
8.2 pt (9%)
3DMark - 3DMark Time Spy Score
719 Points (4%)
3DMark - 3DMark Time Spy Graphics
631 Points (3%)
3DMark - 3DMark Ice Storm Extreme Graphics
66347 Points (9%)
3DMark - 3DMark Cloud Gate Score
13310 Points (17%)
3DMark - 3DMark Cloud Gate Graphics
18491 Points (9%)
3DMark - 3DMark Fire Strike Standard Score
2322 Points (6%)
3DMark - 3DMark Fire Strike Standard Graphics
2430 Points (5%)
3DMark - 3DMark Ice Storm Graphics
73348 Points (10%)
3DMark 11 - 3DM11 Performance Score
3216 Points (8%)
3DMark 11 - 3DM11 Performance GPU
2911 Points (5%)
3DMark Vantage
3DM Vant. Perf. total + NVIDIA Quadro 5000M
3DMark Vantage - 3DM Vant. Perf. total
min: 7700     avg: 7767     median: 7766.5 (7%)     max: 7833 Points
3DM Vant. Perf. total + NVIDIA Quadro M600M
12734 Points (12%)
3DM Vant. Perf. GPU no PhysX + NVIDIA Quadro 5000M
3DMark Vantage - 3DM Vant. Perf. GPU no PhysX
7015 Points (6%)
3DM Vant. Perf. GPU no PhysX + NVIDIA Quadro M600M
10958 Points (10%)
3DMark 03 - 3DMark 03 - Standard
41650 Points (22%)
3DMark 05 - 3DMark 05 - Standard
18903 Points (28%)
3DMark 06 3DMark 06 - Standard 1280x1024 + NVIDIA Quadro 5000M
3DMark 06
12967 Points (21%)
3DMark 06 - Standard 1280x1024 + NVIDIA Quadro M600M
20563 Points (34%)
3DMark 06 - Standard 1280x768 + NVIDIA Quadro 5000M
3DMark 06
13127 Points (21%)
SPECviewperf 11
specvp11 snx-01 + NVIDIA Quadro 5000M
SPECviewperf 11 - specvp11 snx-01
min: 28.13     avg: 28.6     median: 28.6 (20%)     max: 29 fps
specvp11 snx-01 + NVIDIA Quadro M600M
34.2 fps (24%)
specvp11 tcvis-02 + NVIDIA Quadro 5000M
SPECviewperf 11 - specvp11 tcvis-02
min: 25.96     avg: 26.4     median: 26.4 (44%)     max: 26.82 fps
specvp11 tcvis-02 + NVIDIA Quadro M600M
36.7 fps (61%)
specvp11 sw-02 + NVIDIA Quadro 5000M
SPECviewperf 11 - specvp11 sw-02
min: 29.99     avg: 30.1     median: 30.1 (36%)     max: 30.2 fps
specvp11 sw-02 + NVIDIA Quadro M600M
47.5 fps (57%)
specvp11 proe-05 + NVIDIA Quadro 5000M
SPECviewperf 11 - specvp11 proe-05
min: 6.4     avg: 6.6     median: 6.6 (27%)     max: 6.71 fps
specvp11 proe-05 + NVIDIA Quadro M600M
16.4 fps (68%)
specvp11 maya-03 + NVIDIA Quadro 5000M
SPECviewperf 11 - specvp11 maya-03
min: 43.9     avg: 44.6     median: 44.6 (34%)     max: 45.2 fps
specvp11 maya-03 + NVIDIA Quadro M600M
51.9 fps (39%)
specvp11 lightwave-01 + NVIDIA Quadro 5000M
SPECviewperf 11 - specvp11 lightwave-01
min: 31.9     avg: 33.3     median: 33.3 (36%)     max: 34.7 fps
specvp11 lightwave-01 + NVIDIA Quadro M600M
52.3 fps (56%)
specvp11 ensight-04 + NVIDIA Quadro 5000M
SPECviewperf 11 - specvp11 ensight-04
min: 28.6     avg: 29     median: 29 (14%)     max: 29.3 fps
specvp11 ensight-04 + NVIDIA Quadro M600M
27.6 fps (13%)
specvp11 catia-03 + NVIDIA Quadro 5000M
SPECviewperf 11 - specvp11 catia-03
min: 25.1     avg: 26.9     median: 26.9 (33%)     max: 28.7 fps
specvp11 catia-03 + NVIDIA Quadro M600M
45.1 fps (55%)
SPECviewperf 12
specvp12 sw-03 + NVIDIA Quadro M600M
SPECviewperf 12 - specvp12 sw-03
52.4 fps (23%)
specvp12 snx-02 + NVIDIA Quadro M600M
SPECviewperf 12 - specvp12 snx-02
24.8 fps (7%)
specvp12 showcase-01 + NVIDIA Quadro M600M
SPECviewperf 12 - specvp12 showcase-01
17.2 fps (7%)
specvp12 mediacal-01 + NVIDIA Quadro M600M
SPECviewperf 12 - specvp12 mediacal-01
7.5 fps (5%)
specvp12 maya-04 + NVIDIA Quadro M600M
SPECviewperf 12 - specvp12 maya-04
22 fps (9%)
specvp12 energy-01 + NVIDIA Quadro M600M
SPECviewperf 12 - specvp12 energy-01
0.5 fps (1%)
specvp12 creo-01 + NVIDIA Quadro M600M
SPECviewperf 12 - specvp12 creo-01
31.7 fps (17%)
specvp12 catia-04 + NVIDIA Quadro M600M
SPECviewperf 12 - specvp12 catia-04
27.6 fps (9%)
Cinebench R10 Cinebench R10 Shading (32bit) + NVIDIA Quadro M600M
Cinebench R10 - Cinebench R10 Shading (32bit)
6832 Points (32%)
Cinebench R11.5 Cinebench R11.5 OpenGL 64 Bit + NVIDIA Quadro 5000M
Cinebench R11.5 - Cinebench R11.5 OpenGL 64 Bit
32.7 fps (12%)
Cinebench R11.5 OpenGL 64 Bit + NVIDIA Quadro M600M
67.1 fps (24%)
Cinebench R15
Cinebench R15 OpenGL 64 Bit + NVIDIA Quadro M600M
Cinebench R15 - Cinebench R15 OpenGL 64 Bit
75.2 fps (20%)
Cinebench R15 OpenGL Ref. Match 64 Bit + NVIDIA Quadro M600M
Cinebench R15 - Cinebench R15 OpenGL Ref. Match 64 Bit
99.6 % (100%)
GFXBench 3.0 - GFXBench 3.0 Manhattan
59.4 fps (16%)
GFXBench 3.0 - GFXBench 3.0 Manhattan Offscreen
104 fps (8%)
GFXBench - GFXBench Car Chase Onscreen
45.9 fps (1%)
GFXBench - GFXBench Car Chase Offscreen
49.8 fps (0%)
LuxMark v2.0 64Bit - LuxMark v2.0 Room GPU
484 Samples/s (2%)
LuxMark v2.0 64Bit - LuxMark v2.0 Sala GPU
1016 Samples/s (2%)
ComputeMark v2.1 - ComputeMark v2.1 Result
1754 Points (4%)
Power Consumption - Furmark Stress Test Power Consumption - external Monitor *
59.5 Watt (9%)
Power Consumption - The Witcher 3 Power Consumption - external Monitor *
48.6 Watt (7%)

Average Benchmarks NVIDIA Quadro 5000M → 100% n=12

Average Benchmarks NVIDIA Quadro M600M → 157% n=12

- 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

Spiele-Benchmarks

Die folgenden Benchmarks basieren auf unseren Spieletests mit Testnotebooks. Die Performance dieser Grafikkarte bei den gelisteten Spielen ist abhängig von der verwendeten CPU, Speicherausstattung, Treiber und auch Betriebssystem. Dadurch müssen die untenstehenden Werte nicht repräsentativ sein. Detaillierte Informationen über das verwendete System sehen Sie nach einem Klick auf den fps-Wert.

For Honor

For Honor

2017
low 1280x720
Quadro M600M:
36.3  fps
med. 1920x1080
Quadro M600M:
24.6  fps
high 1920x1080
Quadro M600M:
23.1  fps
ultra 1920x1080
Quadro M600M:
16  fps
low 1280x720
Quadro M600M:
73.7  fps
med. 1366x768
Quadro M600M:
42.7  fps
high 1920x1080
Quadro M600M:
18.3  fps
ultra 1920x1080
Quadro M600M:
16.3  fps
low 1280x720
Quadro M600M:
29  fps
med. 1366x768
Quadro M600M:
21.6  fps
high 1920x1080
Quadro M600M:
11.5  fps
ultra 1920x1080
Quadro M600M:
5.8  fps
low 1024x768
Quadro M600M:
46.2  fps
med. 1366x768
Quadro M600M:
28.6  fps
high 1920x1080
Quadro M600M:
15.3  fps
ultra 1920x1080
Quadro M600M:
12.7  fps
low 1024x768
Quadro M600M:
83  fps
med. 1366x768
Quadro M600M:
47.9  fps
high 1920x1080
Quadro M600M:
21.4  fps
ultra 1920x1080
Quadro M600M:
18.5  fps
low 1024x768
Quadro M600M:
43  fps
med. 1366x768
Quadro M600M:
26.2  fps
high 1920x1080
Quadro M600M:
14.2  fps
ultra 1920x1080
Quadro M600M:
7.6  fps
low 1024x768
Quadro M600M:
103.9  fps
med. 1366x768
Quadro M600M:
65.2  fps
high 1366x768
Quadro M600M:
47.1  fps
ultra 1920x1080
Quadro M600M:
20.6  fps
low 1280x720
Quadro M600M:
127.6  fps
med. 1366x768
Quadro M600M:
80.2  fps
high 1366x768
Quadro M600M:
71.7  fps
ultra 1920x1080
Quadro M600M:
26.9  fps

Eine Liste mit weiteren Spielen und allen Grafikkarten finden Sie auf unserer Seite: Welches Spiel ist mit welcher Grafikkarte spielbar?

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 23. 10:07:03

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

#1 checking url part for id 6510 +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, 20 Jan 2022 16:23:38 +0100 +0s ... 0s

#4 linkCache_getLink using $NBC_LINKCACHE +0.066s ... 0.067s

#5 linkCache_getLink using $NBC_LINKCACHE +0.005s ... 0.072s

#6 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.072s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#22 composed specs +0s ... 0.073s

#23 did output specs +0s ... 0.073s

#24 start showIntegratedCPUs +0s ... 0.073s

#25 getting avg benchmarks for device 1939 +0.029s ... 0.102s

#26 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.103s

#27 got single benchmarks 1939 +0.005s ... 0.108s

#28 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.111s

#29 getting avg benchmarks for device 6510 +0.003s ... 0.114s

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

#31 got single benchmarks 6510 +0.006s ... 0.12s

#32 got avg benchmarks for devices +0s ... 0.12s

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

#34 linkCache_getLink no uid found +0s ... 0.121s

#35 linkCache_getLink no uid found +0s ... 0.121s

#36 linkCache_getLink no uid found +0s ... 0.122s

#37 linkCache_getLink no uid found +0s ... 0.122s

#38 linkCache_getLink no uid found +0s ... 0.122s

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

#40 linkCache_getLink no uid found +0s ... 0.123s

#41 linkCache_getLink no uid found +0s ... 0.123s

#42 linkCache_getLink no uid found +0.001s ... 0.124s

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

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

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

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

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

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

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

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

#51 linkCache_getLink no uid found +0s ... 0.126s

#52 linkCache_getLink no uid found +0s ... 0.127s

#53 linkCache_getLink no uid found +0s ... 0.127s

#54 linkCache_getLink no uid found +0s ... 0.127s

#55 linkCache_getLink no uid found +0s ... 0.127s

#56 linkCache_getLink no uid found +0s ... 0.128s

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

#58 linkCache_getLink no uid found +0s ... 0.128s

#59 linkCache_getLink no uid found +0s ... 0.128s

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

#61 linkCache_getLink no uid found +0s ... 0.128s

#62 linkCache_getLink no uid found +0s ... 0.129s

#63 linkCache_getLink no uid found +0s ... 0.129s

#64 linkCache_getLink no uid found +0s ... 0.129s

#65 linkCache_getLink no uid found +0s ... 0.129s

#66 linkCache_getLink no uid found +0s ... 0.129s

#67 linkCache_getLink no uid found +0s ... 0.129s

#68 linkCache_getLink no uid found +0s ... 0.13s

#69 linkCache_getLink no uid found +0s ... 0.13s

#70 linkCache_getLink no uid found +0s ... 0.13s

#71 linkCache_getLink no uid found +0s ... 0.13s

#72 linkCache_getLink no uid found +0s ... 0.13s

#73 linkCache_getLink no uid found +0s ... 0.131s

#74 linkCache_getLink no uid found +0s ... 0.131s

#75 linkCache_getLink no uid found +0s ... 0.131s

#76 linkCache_getLink no uid found +0s ... 0.131s

#77 linkCache_getLink no uid found +0s ... 0.131s

#78 linkCache_getLink no uid found +0s ... 0.132s

#79 linkCache_getLink no uid found +0s ... 0.132s

#80 linkCache_getLink no uid found +0s ... 0.132s

#81 linkCache_getLink no uid found +0s ... 0.133s

#82 linkCache_getLink no uid found +0s ... 0.133s

#83 linkCache_getLink no uid found +0s ... 0.133s

#84 linkCache_getLink no uid found +0s ... 0.134s

#85 linkCache_getLink no uid found +0s ... 0.134s

#86 linkCache_getLink no uid found +0s ... 0.134s

#87 linkCache_getLink no uid found +0s ... 0.135s

#88 linkCache_getLink no uid found +0s ... 0.135s

#89 linkCache_getLink no uid found +0s ... 0.135s

#90 linkCache_getLink no uid found +0s ... 0.136s

#91 linkCache_getLink no uid found +0s ... 0.136s

#92 linkCache_getLink no uid found +0s ... 0.136s

#93 linkCache_getLink no uid found +0s ... 0.137s

#94 linkCache_getLink no uid found +0s ... 0.137s

#95 linkCache_getLink no uid found +0s ... 0.138s

#96 linkCache_getLink no uid found +0s ... 0.138s

#97 linkCache_getLink no uid found +0s ... 0.138s

#98 linkCache_getLink no uid found +0s ... 0.139s

#99 min, max, avg, median took s +0s ... 0.139s

#100 before gaming benchmark output +0s ... 0.139s

#101 Got 32 rows for game benchmarks. +0.004s ... 0.144s

#102 composed SQL query for gamebenchmarks +0s ... 0.144s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#127 got data and put it in $dataArray +0s ... 0.144s

#128 linkCache_getLink no uid found +0.001s ... 0.145s

#129 linkCache_getLink no uid found +0s ... 0.145s

#130 linkCache_getLink no uid found +0s ... 0.145s

#131 linkCache_getLink no uid found +0s ... 0.146s

#132 linkCache_getLink no uid found +0.001s ... 0.146s

#133 linkCache_getLink no uid found +0s ... 0.146s

#134 linkCache_getLink no uid found +0s ... 0.146s

#135 linkCache_getLink no uid found +0s ... 0.146s

#136 linkCache_getLink no uid found +0.001s ... 0.147s

#137 linkCache_getLink no uid found +0s ... 0.147s

#138 linkCache_getLink no uid found +0s ... 0.147s

#139 linkCache_getLink no uid found +0s ... 0.147s

#140 linkCache_getLink no uid found +0.001s ... 0.148s

#141 linkCache_getLink no uid found +0s ... 0.148s

#142 linkCache_getLink no uid found +0s ... 0.148s

#143 linkCache_getLink no uid found +0s ... 0.148s

#144 linkCache_getLink no uid found +0.001s ... 0.148s

#145 linkCache_getLink no uid found +0s ... 0.148s

#146 linkCache_getLink no uid found +0s ... 0.148s

#147 linkCache_getLink no uid found +0s ... 0.148s

#148 linkCache_getLink no uid found +0.001s ... 0.149s

#149 linkCache_getLink no uid found +0s ... 0.149s

#150 linkCache_getLink no uid found +0s ... 0.149s

#151 linkCache_getLink no uid found +0s ... 0.149s

#152 linkCache_getLink no uid found +0.001s ... 0.149s

#153 linkCache_getLink no uid found +0s ... 0.149s

#154 linkCache_getLink no uid found +0s ... 0.15s

#155 linkCache_getLink no uid found +0s ... 0.15s

#156 linkCache_getLink no uid found +0.001s ... 0.15s

#157 linkCache_getLink no uid found +0s ... 0.15s

#158 linkCache_getLink no uid found +0s ... 0.15s

#159 linkCache_getLink no uid found +0s ... 0.15s

#160 benchmarks composed for output. +0s ... 0.15s

#161 calculated avg scores. +0s ... 0.15s

#162 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.151s

#163 return log +0.003s ... 0.154s

Teilen Sie diesen Artikel um uns zu unterstützen. Jeder Link hilft!
> Notebook Test, Laptop Test und News > Benchmarks / Technik > Benchmarks / Technik > Grafikkarten Vergleich - Head 2 Head
Autor: Redaktion,  8.09.2017 (Update: 19.05.2020)