Notebookcheck Logo

NVIDIA Quadro 2000M vs NVIDIA Quadro 3000M

NVIDIA Quadro 2000M

► remove from comparison

Die NVIDIA Quadro 2000M 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 460M bzw GT 555M, bietet ebenfalls 192  Shader (hier genannt CUDA Cores) jedoch nur einen 128 Bit Speicherbus mit DDR3 Grafikspeicher. Die Quadro 2000M ist für die Huron River Plattform (Sandy Bridge) gedacht und wurde von der Quadro K2000M für Ivy Bridge Notebooks abgelöst.

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 Quadro 2000M 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 relativ langsamen DDR3 Grafikspeicher in Verbindung mit dem 128 Bit Speicherbus, kann die 2000M nur 28.8 GB/s übertragen (3000M 80GB/s) und kann dadurch deutlich gebremst werden.

Die Nvidia Quadro 2000M ist kompatibel mit der Steroscopic-Lösung NVIDIA 3D Vision Pro. Weiters wird auch Optimus unterstützt, wodurch automatisch zwischen Prozessorgrafik und Quadro umgeschaltet werden kann (wenn vom Notebookhersteller verbaut).

Die Nvidia Quadro 2000M ist mit 55 Watt TGP spezifiziert und eignet sich daher für Mittelklasse-Notebooks mit 15" Display.

NVIDIA Quadro 3000M

► remove from comparison

Die NVIDIA Quadro 3000M 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 470M, bietet jedoch 240 Shader (hier genannt CUDA Cores). Sie ist ähnlich wie die 470M mit 75W TDP spezifizert und bietet im Vergleich zu 5010M (100 Watt TDP) keine Unterstützung für ECC Speicher oder Double-Precision-Gleitkommaberechnungen.

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 Quadro 3000M 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.

Die theoretische Rechenleistung sollte sich auf dem Niveau der Consumer GTX 460M bewegen. Diese hat zwar weniger Shader aber eine höhere Taktrate.

Durch den Einsatz von schnellem GDDR5 Grafikspeicher, sollte der 256 Bit Speicherbus nicht zum Flaschenhals der Grafikkarte werden und kann bis zu 80 GB / Sekunde übertragen (5010M 83.2 GB/s, 5000M 76.8 GB/s).

Die Nvidia Quadro 3000M ist kompatibel mit der Steroscopic-Lösung NVIDIA 3D Vision Pro. Weiters wird auch Optimus unterstützt, wodurch automatisch zwischen Prozessorgrafik und Quadro umgeschaltet werden kann (wenn vom Notebookhersteller verbaut).

Wie auch die GeForce GTX 470M, ist die Quadro 3000M mit 75 Watt TDP spezifiziert  und eignet sich daher nur für große und schwere 17" Notebooks.

NVIDIA Quadro 2000MNVIDIA Quadro 3000M
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 compare 384 @ 0.84 - 0.88 GHz128 Bit @ 5012 MHz
Quadro M500M compare 384 @ 1.03 - 1.12 GHz64 Bit @ 4004 MHz
Quadro 5000M compare 320 @ 0.41 GHz256 Bit @ 1200 MHz
Quadro 3000M 240 @ 0.45 GHz256 Bit @ 625 MHz
Quadro 2000M 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 compare 384 @ 0.84 - 0.88 GHz128 Bit @ 5012 MHz
Quadro M500M compare 384 @ 1.03 - 1.12 GHz64 Bit @ 4004 MHz
Quadro 5000M compare 320 @ 0.41 GHz256 Bit @ 1200 MHz
Quadro 3000M 240 @ 0.45 GHz256 Bit @ 625 MHz
Quadro 2000M 192 @ 0.55 GHz128 Bit @ 900 MHz
Quadro 1000M compare 96 @ 0.7 GHz128 Bit @ 900 MHz
CodenameFermiFermi
ArchitekturFermiFermi
Pipelines192 - unified240 - unified
Kerntakt550 MHz450 MHz
Shadertakt1100 MHz900 MHz
Speichertakt900 MHz625 MHz
Speicherbandbreite128 Bit256 Bit
SpeichertypDDR3GDDR5
Max. Speichergröße2048 MB2048 MB
Shared Memoryneinnein
APIDirectX 11, Shader 5.0DirectX 11, Shader 5.0
Stromverbrauch55 Watt75 Watt
Herstellungsprozess40 nm40 nm
FeaturesOpenGl 4.1, FP32OpenGl 4.1, FP32
Notebookgrößemittel (15.4" z.B.)groß (17" z.B.)
Erscheinungsdatum22.02.2011 22.02.2011

Benchmarks

3DMark 11 - 3DM11 Performance Score
min: 1416     avg: 1422     median: 1421 (3%)     max: 1428 Points
1742 Points (4%)
3DMark 11 - 3DM11 Performance GPU
min: 1259     avg: 1261     median: 1261 (2%)     max: 1263 Points
1539 Points (2%)
3DMark Vantage
3DM Vant. Perf. total + NVIDIA Quadro 2000M
3DMark Vantage - 3DM Vant. Perf. total
min: 6608     avg: 6634     median: 6633.5 (2%)     max: 6659 Points
3DM Vant. Perf. total + NVIDIA Quadro 3000M
7941 Points (2%)
3DM Vant. Perf. GPU no PhysX + NVIDIA Quadro 2000M
3DMark Vantage - 3DM Vant. Perf. GPU no PhysX
min: 5391     avg: 5411     median: 5410.5 (4%)     max: 5430 Points
3DM Vant. Perf. GPU no PhysX + NVIDIA Quadro 3000M
min: 6604     avg: 6661     median: 6660.5 (5%)     max: 6717 Points
3DMark 05 - 3DMark 05 - Standard
21287 Points (30%)
3DMark 06 3DMark 06 - Standard 1280x1024 + NVIDIA Quadro 2000M
3DMark 06
min: 11575     avg: 11659     median: 11656 (18%)     max: 11747 Points
3DMark 06 - Standard 1280x1024 + NVIDIA Quadro 3000M
min: 14054     avg: 14221     median: 14220.5 (21%)     max: 14387 Points
Unigine Heaven 2.1 - Heaven 2.1 high
min: 14.1     avg: 17     median: 17 (3%)     max: 19.8 fps
SPECviewperf 11
specvp11 snx-01 + NVIDIA Quadro 2000M
SPECviewperf 11 - specvp11 snx-01
min: 19.28     avg: 19.3     median: 19.3 (14%)     max: 19.32 fps
specvp11 snx-01 + NVIDIA Quadro 3000M
20.4 fps (15%)
specvp11 tcvis-02 + NVIDIA Quadro 2000M
SPECviewperf 11 - specvp11 tcvis-02
min: 22.13     avg: 22.3     median: 22.3 (37%)     max: 22.52 fps
specvp11 tcvis-02 + NVIDIA Quadro 3000M
22.9 fps (38%)
specvp11 sw-02 + NVIDIA Quadro 2000M
SPECviewperf 11 - specvp11 sw-02
min: 32.8     avg: 33.1     median: 33.1 (40%)     max: 33.4 fps
specvp11 sw-02 + NVIDIA Quadro 3000M
30.1 fps (36%)
specvp11 proe-05 + NVIDIA Quadro 2000M
SPECviewperf 11 - specvp11 proe-05
min: 9.45     avg: 9.6     median: 9.6 (40%)     max: 9.83 fps
specvp11 proe-05 + NVIDIA Quadro 3000M
7.6 fps (32%)
specvp11 maya-03 + NVIDIA Quadro 2000M
SPECviewperf 11 - specvp11 maya-03
min: 45.28     avg: 45.6     median: 45.6 (34%)     max: 45.96 fps
specvp11 maya-03 + NVIDIA Quadro 3000M
42.5 fps (32%)
specvp11 lightwave-01 + NVIDIA Quadro 2000M
SPECviewperf 11 - specvp11 lightwave-01
min: 40.8     avg: 41.9     median: 41.9 (45%)     max: 42.93 fps
specvp11 lightwave-01 + NVIDIA Quadro 3000M
34.7 fps (37%)
specvp11 ensight-04 + NVIDIA Quadro 2000M
SPECviewperf 11 - specvp11 ensight-04
min: 17.84     avg: 17.9     median: 17.9 (9%)     max: 17.96 fps
specvp11 ensight-04 + NVIDIA Quadro 3000M
18.3 fps (9%)
specvp11 catia-03 + NVIDIA Quadro 2000M
SPECviewperf 11 - specvp11 catia-03
min: 27.08     avg: 27.4     median: 27.4 (33%)     max: 27.69 fps
specvp11 catia-03 + NVIDIA Quadro 3000M
24.6 fps (30%)
Windows 7 Experience Index - Win7 Gaming graphics
6.9 Points (87%)
Windows 7 Experience Index - Win7 Graphics
6.9 Points (87%)
Cinebench R10 Cinebench R10 Shading (32bit) + NVIDIA Quadro 2000M
Cinebench R10 - Cinebench R10 Shading (32bit)
5671 Points (24%)
Cinebench R10 Shading (32bit) + NVIDIA Quadro 3000M
6519 Points (28%)
Cinebench R11.5 Cinebench R11.5 OpenGL 64 Bit + NVIDIA Quadro 2000M
Cinebench R11.5 - Cinebench R11.5 OpenGL 64 Bit
min: 38.3     avg: 38.4     median: 38.4 (14%)     max: 38.44 fps
Cinebench R11.5 OpenGL 64 Bit + NVIDIA Quadro 3000M
min: 45.4     avg: 45.5     median: 45.5 (17%)     max: 45.65 fps

Average Benchmarks NVIDIA Quadro 2000M → 100% n=15

Average Benchmarks NVIDIA Quadro 3000M → 106% 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

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.

low 800x600
100%
Quadro 2000M:
86.7  fps
med. 1024x768
100%
Quadro 2000M:
75  fps
high 1360x768
100%
Quadro 2000M:
71.7  fps
ultra 1920x1080
100%
Quadro 2000M:
41.7  fps
Fifa 11

Fifa 11

2010
high 1360x768
100%
Quadro 2000M:
92  fps
224%
Quadro 3000M:
206.2  fps
ultra 1920x1080
100%
Quadro 2000M:
59  fps
216%
Quadro 3000M:
127.3  fps
Mafia 2

Mafia 2

2010
low 800x600
100%
Quadro 2000M:
92  fps
med. 1024x768
100%
Quadro 2000M:
71  fps
high 1360x768
100%
Quadro 2000M:
59.1  fps
ultra 1920x1080
100%
Quadro 2000M:
35.1  fps
low 1024x768
100%
Quadro 2000M:
165 243 ~ 204 fps
med. 1360x768
100%
Quadro 2000M:
82  fps
high 1360x768
100%
Quadro 2000M:
45  fps
ultra 1920x1080
100%
Quadro 2000M:
23 37 ~ 30 fps
med. 1360x768
Quadro 3000M:
53.8  fps
ultra 1920x1080
Quadro 3000M:
11.5  fps
med. 1366x768
100%
Quadro 2000M:
64.6  fps
high 1366x768
100%
Quadro 2000M:
46.9  fps
ultra 1920x1080
100%
Quadro 2000M:
22.8  fps
low 800x600
100%
Quadro 2000M:
200.3  fps
med. 1024x768
100%
Quadro 2000M:
74.8  fps
high 1366x768
100%
Quadro 2000M:
59.5  fps
ultra 1920x1080
100%
Quadro 2000M:
37.6  fps
Risen

Risen

2009
med. 1024x768
Quadro 3000M:
66.7  fps
high 1366x768
Quadro 3000M:
39.6  fps
ultra 1920x1080
Quadro 3000M:
30.4  fps
Need for Speed Shift

Need for Speed Shift

2009
med. 1024x768
Quadro 3000M:
104.8  fps
high 1366x768
Quadro 3000M:
70.9  fps
ultra 1920x1080
Quadro 3000M:
43.3  fps
Colin McRae: DIRT 2

Colin McRae: DIRT 2

2009
med. 1024x768
Quadro 3000M:
113.5  fps
high 1360x768
Quadro 3000M:
71.4  fps
ultra 1920x1080
Quadro 3000M:
40  fps
Anno 1404

Anno 1404

2009
low 1024x768
100%
Quadro 2000M:
62  fps
303%
Quadro 3000M:
187.6  fps
ultra 1280x1024
100%
Quadro 2000M:
36 43 ~ 40 fps
131%
Quadro 3000M:
52.4  fps
Sims 3

Sims 3

2009
low 800x600
100%
Quadro 2000M:
269  fps
med. 1024x768
100%
Quadro 2000M:
93  fps
high 1280x1024
100%
Quadro 2000M:
47.9  fps

Average Gaming NVIDIA Quadro 2000M → 100%

Average Gaming 30-70 fps → 100%

Average Gaming NVIDIA Quadro 3000M → 218%

Average Gaming 30-70 fps → 131%

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 05. 14:04:14

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

#1 checking url part for id 2433 +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 Mon, 04 Jul 2022 17:25:59 +0200 +0s ... 0s

#4 linkCache_getLink using $NBC_LINKCACHE +0.005s ... 0.006s

#5 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.008s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#25 getting avg benchmarks for device 2435 +0.03s ... 0.038s

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

#27 got single benchmarks 2435 +0.007s ... 0.045s

#28 getting avg benchmarks for device 2433 +0s ... 0.045s

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

#30 got single benchmarks 2433 +0.004s ... 0.049s

#31 got avg benchmarks for devices +0s ... 0.049s

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

#33 linkCache_getLink no uid found +0.001s ... 0.05s

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

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

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

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

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

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

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

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

#42 linkCache_getLink no uid found +0s ... 0.052s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#88 min, max, avg, median took s +0s ... 0.059s

#89 before gaming benchmark output +0s ... 0.059s

#90 Got 44 rows for game benchmarks. +0.004s ... 0.063s

#91 composed SQL query for gamebenchmarks +0s ... 0.063s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#112 got data and put it in $dataArray +0.002s ... 0.065s

#113 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.067s

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

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

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

#117 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.068s

#118 linkCache_getLink no uid found +0s ... 0.069s

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

#120 linkCache_getLink no uid found +0s ... 0.069s

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

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

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

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

#125 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.07s

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

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

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

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

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

#131 linkCache_getLink no uid found +0.001s ... 0.071s

#132 linkCache_getLink no uid found +0s ... 0.071s

#133 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.072s

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

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

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

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

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

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

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

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

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

#143 linkCache_getLink no uid found +0.001s ... 0.075s

#144 linkCache_getLink no uid found +0s ... 0.075s

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

#146 linkCache_getLink no uid found +0.001s ... 0.076s

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

#148 linkCache_getLink no uid found +0s ... 0.076s

#149 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.076s

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

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

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

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

#154 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.077s

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

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

#157 benchmarks composed for output. +0s ... 0.077s

#158 calculated avg scores. +0s ... 0.077s

#159 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.078s

#160 return log +0.003s ... 0.081s

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)