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

NVIDIA GeForce GTX 285M vs NVIDIA GeForce GTX 260M

NVIDIA GeForce GTX 285M

► remove from comparison NVIDIA GeForce GTX 285M

Die Nvidia GeForce GTX 285M ist die High-End Grafikkarte der 200M Serie und basiert auf den G92b Kern (Desktop GeForce 9800 GTX+) und ist daher nicht mit der Desktop GTX 285 vergleichbar. Der Chip wird wie der GTX 280M im 55nm Verfahren gefertigt und hat alle 128 Pipelines freigeschaltet (9800M GTX nur 112). Im Vergleich zur GeForce GTX 280M, wird die GTX 285M minimal höher getaktet. Dadurch ist die GTX285M im Schnitt 3-6% schneller als eine GTX280M.

Eine weitere Neuerung im Vergleich mit der 9800M GTX, sind die deutlich beschleunigten Umschaltzeiten bei Hybrid Power (unter 1 Sekunde versus 7 Sekunden bei der 9800M GTX).

Wie alle DirectX 10 Grafikkarten besitzt auch der GeForce GTX 285M "Unified Shader". Es existieren keine dedizierten Pixel- bzw Vertexshader mehr, sondern 128 so genannte Stream Prozessoren übernehmen einfach die anstehende Grafikarbeit (die früher die Pixel und Vertex Shader übernommen haben). Weiters sind die Shadereinheiten höher getaktet als der Chip.

Die Performance der GeForce GTX 285M liegt mit max 6% nur minimal überhalb der GTX 280M und ist dadurch die schnellste Single Chip Karte von Nvidia im ersten Quartal 2010. Sie konkurriert gegen die Mobility Radeon HD 5870 welche dank GDDR5 Speicher und 800 Shader (5-dimensional jedoch) schneller rechnet. Trotzdem, ist die Karte für Spielefreunde eine sehr gute Wahl und sollte alle aktuellen Spiele ruckelfrei in hohen Details und Auflösungen (ausser ev. GTA4) darstellen können. Erst die Nachfolgegrafikkarte, GeForce GTX 480M kan die HD 5870 schlagen und bietet dank DirectX 11 Support und neuer Fermi Architektur deutliche Vorteile.

Die Spieleleistung der GTX 285M reicht um alle aktuellen Spiele (in 2010) mit mind. mittlerer Detailstufe flüssig darstellen zu können. Sehr anspruchsvolle Spiele wie Metro 2033 oder Crysis Warhead können nicht mit maximalen Detailstufen flüssig gespielt werden, alle anderen und älteren Spiele sollten jedoch in FullHD und max. Details flüssig laufen. Mehr Details dazu in der Spieleliste weiter unten.

Ein Vorteil der GeForce GTX 285M ist der integrierte PureVideo HD Videoprozessor (noch VP2). Dieser kann bei der Dekodierung von H.264-, VC-1-, MPEG2- und WMV9 Videomaterial in HD Qualität mithelfen und dadurch die CPU entlasten.

HybridPower ermöglicht das Umschalten zwischen onboard Grafik (mit Nvidia Chipsatz) und dedizierter Grafikkarte (GTX 285M) in Windows Vista. Dadurch kann die dedizierte Grafikkarte abgeschaltet werden, wenn sie nicht benötigt wird (Office, Surfen) und dadurch Energie gespart werden. Hybrid Power kann im Vista Betrieb umgeschaltet werden (derzeit noch manuell per Tool, später lt. Nvidia automatisch im Treiber). GeforceBoost funktioniert mit der GTX 285M nicht, da sie von der Zusammenschaltung mit der Chipsatzgrafik (SLI) nicht profitieren würde.

Der Stromverbrauch von bis zu 75 Watt (des ganzen Boards) erlaubt den Einsatz der Karte nur in Notebooks mit einem leistungsstarken Kühlsystems. Daher ist die GTX 200M Serie nur in schweren und großen Notebooks zu finden.

Im Vergleich zu Desktop Grafikkarten sollte die Leistung zwischen einer 9800 GT und einer 9800 GTX (mit 675/1675/1100) liegen.

NVIDIA GeForce GTX 260M

► remove from comparison NVIDIA GeForce GTX 260M

Die Nvidia GeForce GTX 260M ist eine High-End Notebook Grafikkarte der GeForce GTX 200M Serie. Der Chip basiert auf den G92b Kern und ist daher ein in 55nm produzierter 9800M GTX mit etwas höheren Taktraten (550/1375/950 versus 500/1250/800). Dadurch ist sie nicht mit der Desktop GTX 260 verwandt, sondern eher mit der Desktop 9800 GT.

Wie alle DirectX 10 Grafikkarten besitzt auch der GeForce GTX 260M "Unified Shader". Es existieren keine dedizierten Pixel- bzw Vertexshader mehr, sondern 112 so genannte Stream Prozessoren übernehmen einfach die anstehende Grafikarbeit (die früher die Pixel und Vertex Shader übernommen haben). Weiters sind die Shadereinheiten höher getaktet als der Chip.

Die Leistung der GTX 260M liegt durch die etwas höhere Taktung minimal über der 9800 GTX. Für aktuelle DirectX 10 Spiele, wie Crysis, World in Conflict, Bioshock oder Age of Conan, reicht die Leistung der Grafikkarte in mittleren bis hohen Details. Ältere Spiele laufen auch in hohen Auflösungen mit allen Details flüssig. Als Speicherausstattung  gibt es bis zu 1024 MB GDDR3.

Ein Vorteil der GeForce GTX 200M Serie ist der integrierte PureVideo HD Videoprozessor. Dieser kann bei der Dekodierung von H.264-, VC-1-, MPEG2- und WMV9 Videomaterial in HD Qualität mithelfen und dadurch die CPU entlasten.

HybridPower ermöglicht das Umschalten zwischen onboard Grafik (mit Nvidia Chipsatz) und dedizierter Grafikkarte (GTX 260M) in Windows Vista. Dadurch kann die dedizierte Grafikkarte abgeschaltet werden, wenn sie nicht benötigt wird (Office, Surfen) und dadurch Energie gespart werden. Hybrid Power kann im Vista Betrieb umgeschaltet werden (derzeit noch manuell per Tool, später lt. Nvidia automatisch im Treiber). GeforceBoost funktioniert mit der GTX 260M nicht, da sie von der Zusammenschaltung mit der Chipsatzgrafik (SLI) nicht profitieren würde.

Der Stromverbrauch von bis zu 75 Watt (des ganzen Boards) erlaubt den Einsatz der Karte nur in Notebooks mit einem leistungsstarken Kühlsystems. Daher ist die 260M nur in schweren und großen Notebooks zu finden.

Im Vergleich zu Desktop Grafikkarten sollte die Leistung etwa auf Niveau der GeForce 9800 GT liegen (600/1500/900).

NVIDIA GeForce GTX 285MNVIDIA GeForce GTX 260M
HerstellerNVIDIANVIDIA
GeForce GTX 200M Serie
GeForce GTX 285M SLI compare 256 @ 0.58 GHz256 Bit @ 1020 MHz
GeForce GTX 280M SLI compare 256 @ 0.59 GHz256 Bit @ 950 MHz
GeForce GTX 260M SLI compare 224 @ 0.55 GHz256 Bit @ 950 MHz
GeForce GTX 285M 128 @ 0.58 GHz256 Bit @ 1020 MHz
GeForce GTX 280M compare 128 @ 0.59 GHz256 Bit @ 950 MHz
GeForce GTX 260M 112 @ 0.55 GHz256 Bit @ 950 MHz
GeForce GTX 285M SLI compare 256 @ 0.58 GHz256 Bit @ 1020 MHz
GeForce GTX 280M SLI compare 256 @ 0.59 GHz256 Bit @ 950 MHz
GeForce GTX 260M SLI compare 224 @ 0.55 GHz256 Bit @ 950 MHz
GeForce GTX 285M 128 @ 0.58 GHz256 Bit @ 1020 MHz
GeForce GTX 280M compare 128 @ 0.59 GHz256 Bit @ 950 MHz
GeForce GTX 260M 112 @ 0.55 GHz256 Bit @ 950 MHz
CodenameN10E-GTX1N10E-GT
ArchitekturG9xG9x
Pipelines128 - unified112 - unified
Kerntakt576 MHz550 MHz
Shadertakt1500 MHz1375 MHz
Speichertakt1020 MHz950 MHz
Speicherbandbreite256 Bit256 Bit
SpeichertypGDDR3GDDR3
Max. Speichergröße1024 MB1024 MB
Shared Memoryneinnein
DirectXDirectX 10, Shader 4.0DirectX 10, Shader 4.0
Transistors754 Million754 Million
Herstellungsprozess55 nm55 nm
FeaturesHybridPower, PureVideo HD (VP2), CUDA, PhysX readyHybridPower, PureVideo HD, CUDA, PhysX ready
Notebookgrößegroß (17" z.B.)groß (17" z.B.)
Erscheinungsdatum02.03.2009 02.03.2009
InformationenMXM 3MXM 3
Herstellerseitehttp://www.nvidia.com/object/product_gef...http://www.nvidia.de/object/product_gefo...

Benchmarks

3DMark Vantage
3DM Vant. Perf. total + NVIDIA GeForce GTX 285M
3DMark Vantage - 3DM Vant. Perf. total
min: 6438     avg: 6521     median: 6498 (6%)     max: 6628 Points
3DM Vant. Perf. total + NVIDIA GeForce GTX 260M
min: 4080     avg: 4953     median: 4901 (5%)     max: 5686 Points
3DM Vant. Perf. GPU no PhysX + NVIDIA GeForce GTX 285M
3DMark Vantage - 3DM Vant. Perf. GPU no PhysX
min: 5501     avg: 5631     median: 5631 (5%)     max: 5761 Points
3DM Vant. Perf. GPU no PhysX + NVIDIA GeForce GTX 260M
min: 3840     avg: 4316     median: 4207 (4%)     max: 5058 Points
3DMark 2001SE - 3DMark 2001 - Standard
min: 32699     avg: 34053     median: 34304 (36%)     max: 34905 Points
3DMark 03 - 3DMark 03 - Standard
37372 Points (20%)
min: 27301     avg: 29794     median: 30595.5 (16%)     max: 30685 Points
3DMark 05 - 3DMark 05 - Standard
min: 18935     avg: 18965     median: 18964.5 (28%)     max: 18994 Points
min: 12669     avg: 14773     median: 15079 (22%)     max: 16611 Points
3DMark 06 3DMark 06 - Standard 1280x1024 + NVIDIA GeForce GTX 285M
3DMark 06
min: 12840     avg: 12989     median: 12988.5 (21%)     max: 13137 Points
3DMark 06 - Standard 1280x1024 + NVIDIA GeForce GTX 260M
min: 9458     avg: 10167     median: 10064 (16%)     max: 11209 Points
3DMark 06 - Standard 1280x800 + NVIDIA GeForce GTX 285M
3DMark 06
13729 Points (22%)
3DMark 06 - Score Unknown Settings + NVIDIA GeForce GTX 260M
3DMark 06
10370 Points (17%)
3DMark 06 - Standard 1280x720 + NVIDIA GeForce GTX 260M
3DMark 06
10075 Points (16%)
Windows 7 Experience Index - Win7 Gaming graphics
min: 6.8     avg: 7.1     median: 7.1 (89%)     max: 7.3 Points
6.8 Points (86%)
Windows 7 Experience Index - Win7 Graphics
min: 6.8     avg: 7.1     median: 7.1 (89%)     max: 7.3 Points
6.8 Points (86%)
Windows Vista Experience Index - Windows Vista Leistungsindex - Grafik (Spiele)
5.8 Points (85%)
Windows Vista Experience Index - Windows Vista Leistungsindex - Grafik
5.9 Points (87%)
Cinebench R10 Cinebench R10 Shading (32bit) + NVIDIA GeForce GTX 285M
Cinebench R10 - Cinebench R10 Shading (32bit)
4941 Points (21%)
Cinebench R10 Shading (32bit) + NVIDIA GeForce GTX 260M
min: 3702     avg: 3966     median: 3917 (17%)     max: 4425 Points
Cinebench R11.5 Cinebench R11.5 OpenGL 64 Bit + NVIDIA GeForce GTX 285M
Cinebench R11.5 - Cinebench R11.5 OpenGL 64 Bit
min: 30.82     avg: 31.4     median: 31.4 (11%)     max: 32.01 fps
Cinebench R11.5 OpenGL 64 Bit + NVIDIA GeForce GTX 260M
28 fps (10%)

Average Benchmarks NVIDIA GeForce GTX 285M → 100% n=9

Average Benchmarks NVIDIA GeForce GTX 260M → 83% n=9

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

Mafia 2

Mafia 2

2010
low 800x600
100%
GeForce GTX 285M:
54.9 fps  fps
med. 1024x768
100%
GeForce GTX 285M:
53.8 fps  fps
84%
GeForce GTX 260M:
45  fps
high 1360x768
100%
GeForce GTX 285M:
52.2 fps  fps
84%
GeForce GTX 260M:
43.8  fps
ultra 1920x1080
100%
GeForce GTX 285M:
36.9 fps  fps
low 1024x768
100%
GeForce GTX 285M:
184 fps  fps
84%
GeForce GTX 260M:
154  fps
high 1360x768
GeForce GTX 260M:
47  fps
ultra 1920x1080
100%
GeForce GTX 285M:
32.8 fps  fps
low 800x600
100%
GeForce GTX 285M:
66.3 fps  fps
med. 1360x768
100%
GeForce GTX 285M:
40.8 fps  fps
high 1600x900
100%
GeForce GTX 285M:
21.4 fps  fps
ultra 1920x1080
100%
GeForce GTX 285M:
13.7 fps  fps
low 1024x768
GeForce GTX 260M:
79.1  fps
med. 1366x768
GeForce GTX 260M:
54.8  fps
high 1366x768
100%
GeForce GTX 285M:
47.2  fps
88%
GeForce GTX 260M:
41.6  fps
ultra 1920x1080
100%
GeForce GTX 285M:
26  fps
89%
GeForce GTX 260M:
23.2  fps
low 800x600
GeForce GTX 260M:
137.4  fps
med. 1024x768
100%
GeForce GTX 285M:
70  fps
84%
GeForce GTX 260M:
59.1  fps
high 1366x768
100%
GeForce GTX 285M:
61.2  fps
91%
GeForce GTX 260M:
55.4  fps
ultra 1920x1080
100%
GeForce GTX 285M:
43.3  fps
92%
GeForce GTX 260M:
40  fps
Risen

Risen

2009
low 800x600
GeForce GTX 260M:
51.3 80.3 ~ 66 fps
med. 1024x768
100%
GeForce GTX 285M:
59.2  fps
78%
GeForce GTX 260M:
41.3 50.5 ~ 46 fps
high 1366x768
100%
GeForce GTX 285M:
43.4  fps
78%
GeForce GTX 260M:
31.7 36.5 ~ 34 fps
ultra 1920x1080
100%
GeForce GTX 285M:
30.3  fps
89%
GeForce GTX 260M:
26.9  fps
Need for Speed Shift

Need for Speed Shift

2009
med. 1024x768
100%
GeForce GTX 285M:
75.8  fps
88%
GeForce GTX 260M:
66.5  fps
high 1366x768
100%
GeForce GTX 285M:
65.3  fps
93%
GeForce GTX 260M:
61  fps
ultra 1920x1080
100%
GeForce GTX 285M:
38.6  fps
101%
GeForce GTX 260M:
39.1  fps
Colin McRae: DIRT 2

Colin McRae: DIRT 2

2009
low 800x600
GeForce GTX 260M:
92  fps
med. 1024x768
100%
GeForce GTX 285M:
99.3  fps
80%
GeForce GTX 260M:
79.2  fps
high 1360x768
100%
GeForce GTX 285M:
66.2  fps
93%
GeForce GTX 260M:
61.5  fps
ultra 1920x1080
100%
GeForce GTX 285M:
32.9  fps
107%
GeForce GTX 260M:
35.3  fps
Anno 1404

Anno 1404

2009
low 1024x768
GeForce GTX 260M:
125.2 133 ~ 129 fps
ultra 1280x1024
100%
GeForce GTX 285M:
46.7  fps
90%
GeForce GTX 260M:
36.2 39 44 49.5 ~ 42 fps
Sims 3

Sims 3

2009
low 800x600
GeForce GTX 260M:
313  fps
med. 1024x768
GeForce GTX 260M:
105  fps
high 1280x1024
GeForce GTX 260M:
89  fps
F.E.A.R. 2

F.E.A.R. 2

2009
low 800x600
GeForce GTX 260M:
132 151.2 ~ 142 fps
med. 1024x768
GeForce GTX 260M:
86.5 89 91.1 ~ 89 fps
high 1280x1024
100%
GeForce GTX 285M:
89.2  fps
77%
GeForce GTX 260M:
63.8 65 67.4 73.4 77.4 ~ 69 fps
ultra 1920x1080
100%
GeForce GTX 285M:
47.6  fps
88%
GeForce GTX 260M:
41.8  fps
GTA IV - Grand Theft Auto

GTA IV - Grand Theft Auto

2008
low 800x600
GeForce GTX 260M:
57.9  fps
med. 1024x768
GeForce GTX 260M:
48  fps
high 1280x1024
GeForce GTX 260M:
36.7  fps
Left 4 Dead

Left 4 Dead

2008
low 640x480
GeForce GTX 260M:
107 135.8 ~ 121 fps
high 1024x768
GeForce GTX 260M:
69 85.8 103.3 111.7 ~ 92 fps
Racedriver: GRID

Racedriver: GRID

2008
low 800x600
GeForce GTX 260M:
105 111.9 ~ 108 fps
med. 1024x768
GeForce GTX 260M:
61.5 72 75.1 ~ 70 fps
high 1280x1024
GeForce GTX 260M:
52.7 53 56.2 59.1 ~ 55 fps
Call of Duty 4 - Modern Warfare

Call of Duty 4 - Modern Warfare

2007
low 800x600
GeForce GTX 260M:
211.3  fps
med. 1024x768
GeForce GTX 260M:
95.2 168.8 ~ 132 fps
high 1280x1024
GeForce GTX 260M:
52.8 67.3 77.8 88.5 ~ 72 fps
Supreme Commander - FA Bench

Supreme Commander - FA Bench

2007
med. 1024x768
GeForce GTX 260M:
53.4  fps
high 1024x768
GeForce GTX 260M:
49.2  fps
Crysis - GPU Benchmark

Crysis - GPU Benchmark

2007
low 1024x768
GeForce GTX 260M:
92 123.7 ~ 108 fps
med. 1024x768
GeForce GTX 260M:
56 57.2 76.9 ~ 63 fps
high 1024x768
100%
GeForce GTX 285M:
50.3  fps
76%
GeForce GTX 260M:
31 38 38.4 39.3 41.9 ~ 38 fps
ultra 1920x1080
100%
GeForce GTX 285M:
13.9  fps
88%
GeForce GTX 260M:
12.2  fps
Crysis - CPU Benchmark

Crysis - CPU Benchmark

2007
low 1024x768
GeForce GTX 260M:
110 129.5 ~ 120 fps
med. 1024x768
GeForce GTX 260M:
49 52.6 76.9 ~ 60 fps
high 1024x768
100%
GeForce GTX 285M:
46.4  fps
78%
GeForce GTX 260M:
30.7 35.5 37 37 39.2 ~ 36 fps
ultra 1920x1080
100%
GeForce GTX 285M:
13  fps
88%
GeForce GTX 260M:
11.5  fps
World in Conflict - Benchmark

World in Conflict - Benchmark

2007
low 800x600
100%
GeForce GTX 285M:
126 fps  fps
med. 1024x768
100%
GeForce GTX 285M:
84 fps  fps
71%
GeForce GTX 260M:
47 72 ~ 60 fps
high 1024x768
100%
GeForce GTX 285M:
53 fps  fps
75%
GeForce GTX 260M:
38 42 ~ 40 fps
Call of Juarez Benchmark

Call of Juarez Benchmark

2006
high 1024x768
100%
GeForce GTX 285M:
36.5 fps  fps
71%
GeForce GTX 260M:
22.7 26.6 27.2 ~ 26 fps
Half Life 2 - Lost Coast Benchmark

Half Life 2 - Lost Coast Benchmark

2005
high 1024x768
GeForce GTX 260M:
158  fps
Quake 4

Quake 4

2005
ultra 1024x768
GeForce GTX 260M:
62  fps
World of Warcraft

World of Warcraft

2005
high 1280x1024
GeForce GTX 260M:
51.8  fps
Counter-Strike Source

Counter-Strike Source

2004
high 1024x768
GeForce GTX 260M:
121 270 ~ 196 fps
Doom 3

Doom 3

2004
ultra 1024x768
GeForce GTX 260M:
178  fps
Quake 3 Arena - Timedemo

Quake 3 Arena - Timedemo

1999
high 1024x768
GeForce GTX 260M:
575  fps

Average Gaming NVIDIA GeForce GTX 285M → 100%

Average Gaming 30-70 fps → 100%

Average Gaming NVIDIA GeForce GTX 260M → 85%

Average Gaming 30-70 fps → 86%

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 25. 19:08:25

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

#1 checking url part for id 1111 +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 Tue, 25 Jan 2022 16:23:41 +0100 +0s ... 0s

#4 linkCache_getLink using $NBC_LINKCACHE +0.043s ... 0.043s

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

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

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

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

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

#10 composed specs +0s ... 0.046s

#11 did output specs +0s ... 0.046s

#12 start showIntegratedCPUs +0s ... 0.046s

#13 getting avg benchmarks for device 1582 +0.025s ... 0.07s

#14 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.071s

#15 got single benchmarks 1582 +0.008s ... 0.079s

#16 getting avg benchmarks for device 1111 +0s ... 0.079s

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

#18 got single benchmarks 1111 +0.015s ... 0.094s

#19 got avg benchmarks for devices +0s ... 0.094s

#20 linkCache_getLink no uid found +0s ... 0.094s

#21 linkCache_getLink no uid found +0s ... 0.094s

#22 linkCache_getLink no uid found +0.001s ... 0.095s

#23 linkCache_getLink no uid found +0s ... 0.095s

#24 linkCache_getLink no uid found +0s ... 0.095s

#25 linkCache_getLink no uid found +0s ... 0.095s

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

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

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

#29 linkCache_getLink no uid found +0s ... 0.096s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#57 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.098s

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

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

#60 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.098s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#89 min, max, avg, median took s +0s ... 0.102s

#90 before gaming benchmark output +0s ... 0.102s

#91 Got 144 rows for game benchmarks. +0.009s ... 0.111s

#92 composed SQL query for gamebenchmarks +0s ... 0.111s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#115 got data and put it in $dataArray +0.004s ... 0.115s

#116 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.117s

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

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

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

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

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

#122 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.118s

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

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

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

#126 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.119s

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

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

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

#130 linkCache_getLink no uid found +0.001s ... 0.121s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#153 linkCache_getLink no uid found +0.001s ... 0.123s

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

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

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

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

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

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

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

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

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

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

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

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

#166 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.124s

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

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

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

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

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

#172 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.124s

#173 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.126s

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

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

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

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

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

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

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

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

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

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

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

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

#186 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.128s

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

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

#189 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.129s

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

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

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

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

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

#195 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.13s

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

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

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

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

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

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

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

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

#204 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.131s

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

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

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

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

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

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

#211 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.132s

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

#213 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.133s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#246 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.136s

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

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

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

#250 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.139s

#251 benchmarks composed for output. +0.002s ... 0.142s

#252 calculated avg scores. +0s ... 0.142s

#253 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.142s

#254 return log +0.003s ... 0.145s

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)