Notebookcheck Logo
, , , , , ,
zu verknüpfen.
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
 

NVIDIA Quadro FX 3500M vs NVIDIA Quadro FX 1700M vs NVIDIA Quadro FX 880M

NVIDIA Quadro FX 3500M

► remove from comparison NVIDIA Quadro FX 3500M

Die NVIDIA Quadro FX 3500M ist der Vorgänger der FX 3600M und eine professionelle Grafiklösung für den mobilen Einsatz. Der Quadro FX 3500M eignet sich insbesondere für CAD, digitale Bild- und Videobearbeitung sowie wissenschaftliche Visualisierungen (laut NVIDIA). Sie basiert auf den Grafikkern der  NVIDIA GeForce Go 7950 GTX und sollte dadurch auch sehr gute DirectX 9 Spieleleistung (für 2007) erwarten lassen (mit modifizierten Treibern). Die Karte wird mit zertifizierten Treibern für professionelle Anwendungen ausgeliefert, die jedoch nicht für Spiele optimiert sind (inoffiziell sollte jedoch auch die manuelle Installation von Forceware Treibern möglich sein).

Die Treiber der Quadro FX Serie sind zertifiziert für CAD Anwendungen (z.B. AutoCad, Inventor, Solidstation, Solid Edge, ...) und DCC Anwendungen (z.B. Maya, 3DS Max, Lightwave 3D, ...) und bieten eine 12-Bit-Präzision für Subpixel, Vollbild-Antialiasing, Hardwarebeschleunigtes Antialiasing für Punkte und Linien und weitere für CAD und DCC optimierte Einstellungen.

Von Nvidia wird die 3000er Serie als Kraftpaket für große Modelle und Datenstrukturen beschrieben.

NVIDIA Quadro FX 1700M

► remove from comparison NVIDIA Quadro FX 1700M

Professionelle Grafikkarte mit zertifizierten Treiber besonders für OpenGL geeignet. Technisch ähnlich wie die Quadro FX 1600M (8700M) basiert die FX 1700M auf den 96x0M Kern (G96), jedoch mit höheren Taktraten. Im Vergleich zur 1600M wird bereits Powermizer 8.0 unterstützt.

Gedacht für Digital Content Creators, Ingenieure, Geowissenschaftler und andere professionelle 3D Anwendungen.

Zertifizierte Treiber garantieren die fehlerfreie und schnellere (im Vergleich zu 8700M) Darstellung von professionellen Programmen (CAD, CCD, Visualisierungssoftware).

NVIDIA Quadro FX 880M

► remove from comparison NVIDIA Quadro FX 880M

Die NVIDIA Quadro FX 880M ist eine professionelle Mittelklasse Grafikkarte für mobile Workstations / Laptops. Sie basiert auf die Nvidia GeForce GT 330M mit etwas geringeren Taktraten und beherrscht dadurch DirectX 10.1. Durch ein spezielles BIOS und Treiber zeigt die Quadro FX 880M eine bessere Performance bei professionellen Anwendungen. Weiters ist die Grafikkarte für die gängigsten 3D Anwendungen (DCC, CAD, Modelling) zertifiziert und sollte dadurch fehlerfrei arbeiten. Außerdem bietet der Treiber verschiedene Profile um sich für die professionellen Anwendungen automatisch zu konfigurieren (ähnlich der Spieleprofile in GeForce Grafiktreibern).

Ohne Last taktet die FX 880M nur mit 135 / 270 / 135 MHz (Kern- / Shader- / Speichertakt) wodurch Strom gespart wird (Werte aus dem Lenovo Thinkpad W510).

Wie die GT330M verwendet auch die FX 880M den GT216 Kern. Dieser basiert laut Nvidia auf die High-End Desktop Architektur (GTX 200) und hat daher auch einige Verbesserungen gegenüber der Vorgängergeneration. Weiters wurde die Micro-Architektur verbessert um Akkulaufzeit und Performance zu steigern.

Die Quadro FX 880M unterstützt die Videodekodierung im Grafikchip (PureVideo HD) für weniger CPU Belastung bei HD Dekodierung. Der verbaute Video Processor 4 (VP4) unterstützt das  vollständige Dekodieren von H.264, VC-1, MPEG-2, und jetzt auch MPEG-4 ASP (DivX oder xVID). Nur MPEG-1 wird nicht unterstützt (jedoch ist der Decodieraufwand hier minimal).

Wie auch bei der alten 9700M GTS übernehmen 48 so genannte Stream Prozessoren die anstehende Grafikarbeit (die früher die Pixel und Vertex Shader übernommen haben). Der Vorteil ist, daß es theortisch keinen Leerlauf der ALUs mehr gibt. Die Streamprozessoren sind bei NVIDIA 1-dimensional (1D) und können pro Takt eine Skalaroperation mit einer MADD- (Addition und Multiplikation) und MUL-Anweisung (Multiplikation) durführen. Ausserdem taktet NVIDIA die Shader-ALUs höher als den restlichen Chip (1100 versus 500 MHz).

Dank CUDADirectX ComputeOpenCL und PhysX Support können die Stream Prozessoren auch für andere Anwendungen (Video Kodierung, Physikeffekte, ...) eingesetzt werden und sind bei solchen Spezialanwendungen deutlich schneller als gängige Hauptprozessoren (durch die hohe Anzahl an Shadern die parallel arbeiten).

Moderne und anspruchsvolle DirectX 10 Spiele (wie Crysis) laufen auf der GT 330M mit mittleren Details bei mittleren Auflösungen flüssig. Da die FX 880M Treiber für professionelle Anwendungen optimiert sind, kann hier die Spieleperformance leiden. Spieler sollten deshalb klar zur GeForce Linie greifen.

Zum automatischen Umschalten auf die integrierte Grafik des Prozessors, unterstützt der Grafikchip Optimus. Dies wurde jedoch z.B. beim W510 nicht verbaut. 

NVIDIA Quadro FX 3500MNVIDIA Quadro FX 1700MNVIDIA Quadro FX 880M
Quadro FX Serie
Quadro FX 3800M 128 @ 0.68 GHz256 Bit @ 1000 MHz
Quadro FX 3700M 128 @ 0.55 GHz256 Bit @ 800 MHz
Quadro FX 2800M 96 @ 0.6 GHz256 Bit @ 1000 MHz
Quadro FX 3600M 96 @ 0.5 GHz256 Bit @ 800 MHz
Quadro FX 1800M 72 @ 0.56 GHz128 Bit @ 1100 MHz
Quadro FX 2700M 48 @ 0.53 GHz256 Bit @ 800 MHz
Quadro FX 880M 48 @ 0.55 GHz128 Bit @ 790 MHz
Quadro FX 3500M 24/8 cores @ 0.58 GHz256 Bit @ 700 MHz
Quadro FX 2500M 24/8 cores @ 0.5 GHz256 Bit @ 600 MHz
Quadro FX 1700M 32 @ 0.63 GHz128 Bit @ 800 MHz
Quadro FX 1600M 32 @ 0.63 GHz128 Bit @ 800 MHz
Quadro FX 1500M 20/7 cores @ 0.38 GHz256 Bit @ 500 MHz
Quadro FX 770M 32 @ 0.5 GHz128 Bit @ 800 MHz
Quadro FX 570M 32 @ 0.48 GHz128 Bit @ 700 MHz
Quadro FX 380M 16 @ 0.63 GHz64 Bit @ 800 MHz
Quadro FX 370M 8 @ 0.58 GHz64 Bit @ 700 MHz
Quadro FX 360M 16 @ 0.4 GHz64 Bit @ 600 MHz
Quadro FX 350M 4/3 cores @ 0.45 GHz64 Bit @ 350 MHz
Quadro FX 3800M 128 @ 0.68 GHz256 Bit @ 1000 MHz
Quadro FX 3700M 128 @ 0.55 GHz256 Bit @ 800 MHz
Quadro FX 2800M 96 @ 0.6 GHz256 Bit @ 1000 MHz
Quadro FX 3600M 96 @ 0.5 GHz256 Bit @ 800 MHz
Quadro FX 1800M 72 @ 0.56 GHz128 Bit @ 1100 MHz
Quadro FX 2700M 48 @ 0.53 GHz256 Bit @ 800 MHz
Quadro FX 880M 48 @ 0.55 GHz128 Bit @ 790 MHz
Quadro FX 3500M 24/8 cores @ 0.58 GHz256 Bit @ 700 MHz
Quadro FX 2500M 24/8 cores @ 0.5 GHz256 Bit @ 600 MHz
Quadro FX 1700M 32 @ 0.63 GHz128 Bit @ 800 MHz
Quadro FX 1600M 32 @ 0.63 GHz128 Bit @ 800 MHz
Quadro FX 1500M 20/7 cores @ 0.38 GHz256 Bit @ 500 MHz
Quadro FX 770M 32 @ 0.5 GHz128 Bit @ 800 MHz
Quadro FX 570M 32 @ 0.48 GHz128 Bit @ 700 MHz
Quadro FX 380M 16 @ 0.63 GHz64 Bit @ 800 MHz
Quadro FX 370M 8 @ 0.58 GHz64 Bit @ 700 MHz
Quadro FX 360M 16 @ 0.4 GHz64 Bit @ 600 MHz
Quadro FX 350M 4/3 cores @ 0.45 GHz64 Bit @ 350 MHz
Quadro FX 3800M 128 @ 0.68 GHz256 Bit @ 1000 MHz
Quadro FX 3700M 128 @ 0.55 GHz256 Bit @ 800 MHz
Quadro FX 2800M 96 @ 0.6 GHz256 Bit @ 1000 MHz
Quadro FX 3600M 96 @ 0.5 GHz256 Bit @ 800 MHz
Quadro FX 1800M 72 @ 0.56 GHz128 Bit @ 1100 MHz
Quadro FX 2700M 48 @ 0.53 GHz256 Bit @ 800 MHz
Quadro FX 880M 48 @ 0.55 GHz128 Bit @ 790 MHz
Quadro FX 3500M 24/8 cores @ 0.58 GHz256 Bit @ 700 MHz
Quadro FX 2500M 24/8 cores @ 0.5 GHz256 Bit @ 600 MHz
Quadro FX 1700M 32 @ 0.63 GHz128 Bit @ 800 MHz
Quadro FX 1600M 32 @ 0.63 GHz128 Bit @ 800 MHz
Quadro FX 1500M 20/7 cores @ 0.38 GHz256 Bit @ 500 MHz
Quadro FX 770M 32 @ 0.5 GHz128 Bit @ 800 MHz
Quadro FX 570M 32 @ 0.48 GHz128 Bit @ 700 MHz
Quadro FX 380M 16 @ 0.63 GHz64 Bit @ 800 MHz
Quadro FX 370M 8 @ 0.58 GHz64 Bit @ 700 MHz
Quadro FX 360M 16 @ 0.4 GHz64 Bit @ 600 MHz
Quadro FX 350M 4/3 cores @ 0.45 GHz64 Bit @ 350 MHz
CodenameG71GLMNB9P-GLMN10P-GLM
ArchitekturG7xG9xGT2xx
Pipelines24 / 8 Pixel- / Vertexshader32 - unified48 - unified
Kerntakt575 MHz625 MHz550 MHz
Speichertakt700 MHz800 MHz790 MHz
Speicherbandbreite256 Bit128 Bit128 Bit
SpeichertypGDDR3GDDR3GDDR3, DDR3
Max. Speichergröße512 MB256 MB1024 MB
Shared Memoryneinneinnein
APIDirectX 9c, Shader 3.0DirectX 10, Shader 4.0DirectX 10.1, Shader 4.1
Stromverbrauch45 Watt50 Watt35 Watt
Transistors278 Million289 Million
Herstellungsprozess90 nm65 nm40 nm
Features12-Bit-Sub-Pixel, 32-Bit-Floating-Point Präzision, 32-Bit Gleitkomma Präzision, 128 Bit Grafikpipeline, Hardware 3D Window Clipping, High Precision Dynamic-Range (DPDR) Technology, Unified Memory Architecture, nView Multi-Display (für Multi-Monitor Unterstützung), PowerMizer Energiesparoptionen, Workstation optimierte Architektur, Rotated-Grid Full-Scene Antialiasing (RG FSAA), Unified Driver Architecture, NVIDIA PureVideo TechnologieOpenGL 2.1, PureVideo HD, Powermizer 8.0, mögliche Schnittstellen: LVDS, DVI, VGA, HDTV, HDCP, HDMI
Notebookgrößegroß (17" z.B.)groß (17" z.B.)mittel (15.4" z.B.)
Erscheinungsdatum01.03.2007 01.10.2008 07.01.2010
Herstellerseitehttp://www.nvidia.com/page/quadrofx_go.h...http://www.nvidia.com/object/product_qua...http://www.nvidia.com/object/product_qua...
Shadertakt1250 MHz1210 MHz
InformationenCG Shading Hochsprache, 32 Bit Gleitkommapräzision, 12 Bit Subpixel Präzision, 128 Bit Genauigkeit der Grafikpipeline, Vertex und Pixelshader Programmierbarkeit, PCI-E Interface, FSAA mit gedrehtem Raster, nView Multidisplay Support, High-Precision Dynamic-Range (HPDR) Technologie, Hardware 3D Clipping nach Fensterkennung, Vollbild Antialiasing

Benchmarks

3DMark Vantage
3DM Vant. Perf. total + NVIDIA Quadro FX 880M
3DMark Vantage - 3DM Vant. Perf. total
min: 2558     avg: 2643     median: 2638.5 (2%)     max: 2735 Points
3DM Vant. Perf. GPU no PhysX + NVIDIA Quadro FX 880M
3DMark Vantage - 3DM Vant. Perf. GPU no PhysX
min: 2128     avg: 2203     median: 2149.5 (2%)     max: 2385 Points
3DMark 2001SE - 3DMark 2001 - Standard
35734 Points (37%)
min: 28169     avg: 32291     median: 33331 (35%)     max: 34331 Points
3DMark 03 - 3DMark 03 - Standard
20736 Points (11%)
18212 Points (10%)
min: 18796     avg: 18980     median: 19002 (10%)     max: 19137 Points
3DMark 05 - 3DMark 05 - Standard
9295 Points (13%)
11550 Points (16%)
min: 13154     avg: 13217     median: 13185 (18%)     max: 13298 Points
3DMark 06 3DMark 06 - Score Unknown Settings + NVIDIA Quadro FX 3500M
3DMark 06
5254 Points (8%)
3DMark 06 - Standard 1280x800 + NVIDIA Quadro FX 1700M
3DMark 06
6302 Points (10%)
3DMark 06 - Standard 1280x1024 + NVIDIA Quadro FX 880M
3DMark 06
min: 6366     avg: 6401     median: 6378 (10%)     max: 6473 Points
3DMark 06 - Standard 1280x768 + NVIDIA Quadro FX 880M
3DMark 06
6392 Points (10%)
SPEC Viewperf 10.0 - SPEC Viewperf 10.0 - 3dsmax
47.8 Points (99%)
SPEC Viewperf 10.0 - SPEC Viewperf 10.0 - Catia
47.6 Points (100%)
SPEC Viewperf 10.0 - SPEC Viewperf 10.0 - Maya
60.1 Points (32%)
SPEC Viewperf 10.0 - SPEC Viewperf 10.0 - SolidWorks
58 Points (86%)
SPEC Viewperf 10.0 - SPEC Viewperf 10.0 - UGS Teamcenter
24.4 Points (63%)
SPECviewperf 11
specvp11 snx-01 + NVIDIA Quadro FX 880M
SPECviewperf 11 - specvp11 snx-01
min: 9.18     avg: 9.7     median: 9.7 (7%)     max: 10.27 fps
specvp11 tcvis-02 + NVIDIA Quadro FX 880M
SPECviewperf 11 - specvp11 tcvis-02
min: 11.04     avg: 11.2     median: 11.2 (19%)     max: 11.32 fps
specvp11 sw-02 + NVIDIA Quadro FX 880M
SPECviewperf 11 - specvp11 sw-02
min: 7.56     avg: 16     median: 16 (19%)     max: 24.45 fps
specvp11 proe-05 + NVIDIA Quadro FX 880M
SPECviewperf 11 - specvp11 proe-05
min: 4.28     avg: 5.2     median: 5.2 (22%)     max: 6.21 fps
specvp11 maya-03 + NVIDIA Quadro FX 880M
SPECviewperf 11 - specvp11 maya-03
min: 6.94     avg: 8     median: 8 (6%)     max: 9.09 fps
specvp11 lightwave-01 + NVIDIA Quadro FX 880M
SPECviewperf 11 - specvp11 lightwave-01
min: 9.81     avg: 23.8     median: 23.8 (26%)     max: 37.84 fps
specvp11 ensight-04 + NVIDIA Quadro FX 880M
SPECviewperf 11 - specvp11 ensight-04
min: 10     avg: 10.3     median: 10.3 (5%)     max: 10.59 fps
specvp11 catia-03 + NVIDIA Quadro FX 880M
SPECviewperf 11 - specvp11 catia-03
min: 8.63     avg: 12.3     median: 12.3 (15%)     max: 15.92 fps
Windows 7 Experience Index - Win7 Gaming graphics
6.4 Points (81%)
Windows 7 Experience Index - Win7 Graphics
6.4 Points (81%)
Cinebench R10 Cinebench R10 Shading (32bit) + NVIDIA Quadro FX 1700M
Cinebench R10 - Cinebench R10 Shading (32bit)
6159 Points (26%)
Cinebench R10 Shading (32bit) + NVIDIA Quadro FX 880M
min: 4809     avg: 4886     median: 4846 (21%)     max: 5002 Points
Cinebench R11.5 Cinebench R11.5 OpenGL 64 Bit + NVIDIA Quadro FX 880M
Cinebench R11.5 - Cinebench R11.5 OpenGL 64 Bit
min: 15.84     avg: 16     median: 16 (6%)     max: 16.14 fps

Average Benchmarks NVIDIA Quadro FX 3500M → 100% n=2

Average Benchmarks NVIDIA Quadro FX 1700M → 106% n=2

Average Benchmarks NVIDIA Quadro FX 880M → 117% n=2

- 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.

Fifa 11

Fifa 11

2010
med. 1024x768
Quadro FX 880M:
129.2  fps
high 1360x768
Quadro FX 880M:
90.5  fps
ultra 1920x1080
Quadro FX 880M:
50.4  fps
low 1024x768
Quadro FX 880M:
155  fps
med. 1360x768
Quadro FX 880M:
42  fps
high 1360x768
Quadro FX 880M:
29  fps
ultra 1920x1080
Quadro FX 880M:
12  fps
low 1024x768
Quadro FX 880M:
58.8  fps
med. 1366x768
Quadro FX 880M:
30.4  fps
high 1366x768
Quadro FX 880M:
16.1  fps
ultra 1920x1080
Quadro FX 880M:
9.7  fps
low 800x600
Quadro FX 880M:
124.1  fps
med. 1024x768
Quadro FX 880M:
42.2  fps
high 1366x768
Quadro FX 880M:
35.4  fps
ultra 1920x1080
Quadro FX 880M:
21  fps
Risen

Risen

2009
low 800x600
Quadro FX 880M:
75.4  fps
med. 1024x768
Quadro FX 880M:
29.8 33.4 ~ 32 fps
high 1366x768
Quadro FX 880M:
18.2 20.6 ~ 19 fps
ultra 1920x1080
Quadro FX 880M:
12.7  fps
Colin McRae: DIRT 2

Colin McRae: DIRT 2

2009
low 800x600
Quadro FX 880M:
79.3  fps
med. 1024x768
Quadro FX 880M:
45.7 47.8 ~ 47 fps
high 1360x768
Quadro FX 880M:
20 39 ~ 30 fps
ultra 1920x1080
Quadro FX 880M:
12.8  fps
Anno 1404

Anno 1404

2009
low 1024x768
Quadro FX 880M:
59.7 60 131 147.3 ~ 100 fps
ultra 1280x1024
Quadro FX 880M:
19 19.1 20.5 23 ~ 20 fps
F.E.A.R. 2

F.E.A.R. 2

2009
low 800x600
Quadro FX 880M:
179.6  fps
med. 1024x768
Quadro FX 880M:
65.9  fps
high 1280x1024
Quadro FX 880M:
42.3  fps
Far Cry 2

Far Cry 2

2008
low 640x480
Quadro FX 880M:
93.3  fps
high 1024x768
Quadro FX 880M:
32.4  fps
Racedriver: GRID

Racedriver: GRID

2008
med. 1024x768
Quadro FX 880M:
48.7  fps
high 1280x1024
Quadro FX 880M:
28.9  fps
Call of Duty 4 - Modern Warfare

Call of Duty 4 - Modern Warfare

2007
low 800x600
Quadro FX 880M:
225.7  fps
med. 1024x768
Quadro FX 880M:
60  fps
high 1280x1024
Quadro FX 880M:
59.9  fps
Supreme Commander - FA Bench

Supreme Commander - FA Bench

2007
med. 1024x768
Quadro FX 880M:
29.9  fps
high 1024x768
Quadro FX 880M:
28.2  fps
Crysis - GPU Benchmark

Crysis - GPU Benchmark

2007
med. 1024x768
Quadro FX 1700M:
33.3  fps
high 1024x768
Quadro FX 1700M:
19.1  fps
Crysis - CPU Benchmark

Crysis - CPU Benchmark

2007
med. 1024x768
Quadro FX 1700M:
29.3  fps
high 1024x768
Quadro FX 1700M:
17.1  fps
F.E.A.R.

F.E.A.R.

2005
low 640x480
Quadro FX 1700M:
378  fps
med. 800x600
Quadro FX 1700M:
152  fps
high 1024x768
Quadro FX 1700M:
59  fps
Quake 3 Arena - Timedemo

Quake 3 Arena - Timedemo

1999
high 1024x768
Quadro FX 1700M:
610  fps

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

v1.17
log 25. 03:47:58

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

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

#2 checking url part for id 1621 +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, 20 May 2022 17:25:18 +0200 +0s ... 0s

#5 linkCache_getLink using $NBC_LINKCACHE +0.058s ... 0.059s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#21 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.061s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#38 composed specs +0s ... 0.061s

#39 did output specs +0s ... 0.061s

#40 start showIntegratedCPUs +0s ... 0.061s

#41 getting avg benchmarks for device 61 +0.042s ... 0.104s

#42 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.105s

#43 got single benchmarks 61 +0.004s ... 0.108s

#44 getting avg benchmarks for device 1087 +0s ... 0.109s

#45 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.109s

#46 got single benchmarks 1087 +0.004s ... 0.113s

#47 getting avg benchmarks for device 1621 +0s ... 0.114s

#48 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.114s

#49 got single benchmarks 1621 +0.01s ... 0.125s

#50 got avg benchmarks for devices +0s ... 0.125s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#104 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.134s

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

#106 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.135s

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

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

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

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

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

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

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

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

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

#116 min, max, avg, median took s +0s ... 0.136s

#117 before gaming benchmark output +0s ... 0.136s

#118 Got 55 rows for game benchmarks. +0.006s ... 0.142s

#119 composed SQL query for gamebenchmarks +0s ... 0.142s

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

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

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

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

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

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

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

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

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

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

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

#131 got data and put it in $dataArray +0.003s ... 0.146s

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

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

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

#135 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.147s

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

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

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

#139 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.149s

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

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

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

#143 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.15s

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

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

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

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

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

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

#150 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.151s

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

#152 linkCache_getLink no uid found +0s ... 0.151s

#153 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.152s

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

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

#156 linkCache_getLink no uid found +0s ... 0.152s

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

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

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

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

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

#162 linkCache_getLink no uid found +0s ... 0.153s

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

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

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

#166 linkCache_getLink no uid found +0s ... 0.153s

#167 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.154s

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

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

#170 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.155s

#171 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.155s

#172 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.156s

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

#174 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.157s

#175 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.157s

#176 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.157s

#177 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.158s

#178 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.158s

#179 linkCache_getLink no uid found +0.001s ... 0.159s

#180 linkCache_getLink no uid found +0s ... 0.159s

#181 linkCache_getLink no uid found +0.001s ... 0.16s

#182 linkCache_getLink no uid found +0s ... 0.16s

#183 linkCache_getLink no uid found +0.001s ... 0.161s

#184 linkCache_getLink no uid found +0s ... 0.161s

#185 linkCache_getLink no uid found +0s ... 0.161s

#186 linkCache_getLink no uid found +0.001s ... 0.163s

#187 benchmarks composed for output. +0s ... 0.163s

#188 calculated avg scores. +0s ... 0.163s

#189 return log +0.001s ... 0.163s

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)