Notebookcheck Logo

NVIDIA GeForce GTX 260M SLI vs NVIDIA GeForce GTX 260M vs NVIDIA GeForce GTX 285M SLI

NVIDIA GeForce GTX 260M SLI

► remove from comparison NVIDIA GeForce GTX 260M SLI

The Nvidia GeForce GTX 260M SLI is a combination of two Nvidia GeForce GTX 260M graphics cards for laptops linked together in SLI mode. The combination can be up to 40% faster than a single GTX 260M if given the proper game or driver support. In fact,some games may even run slower under SLI than with a single 260M if driver support is poor. Regardless, current consumption is twice as high as a single 260M. Notably, Nvidia drivers support the deactivation of SLI to save power. This is in contrast to the Catalyst drivers of the 4870 X2 at the time of our review.

The graphics memory of both cards can't be added and compared to single cards, as each card stores the same information. Therefore, a GTX 260M SLI with 2x512 graphics memory only counts as 512 MB for games.

As all SLI combinations, the GeForce 260M SLI may suffer from noticeable micro stuttering at frame rates between 20 to 30 fps. This is due to the inconsistent delays between subsequent frames being rendered and shown onscreen. As a result, an SLI combination may need higher frame rates for fluent gameplay.

Similar to other cards with DirectX 10 capabilities, the GeForce GTX 260M SLI combination renders 3D images using "Unified Shaders". Dedicated pixel shaders and vertex shaders have been dropped in favor of 2x112 stream processors for rendering graphic work that would have normally been done by specialized pixel and vertex shaders. Furthermore, the shader units are higher clocked than the chip at 1375 MHz.

The performance of the GTX 260M SLI is in the region of a single GTX 260M, but can be about 40 percent higher depending on application and driver support. A single GTX 260M is only a bit faster than a 9800M GTX due to the higher clock speed. For current DirectX 10 games like Crysis, World in Conflict, Bioshock or Age of Conan, the performance of this graphics card is sufficient with medium and high details. Older games and less demanding ones run fluently with high resolutions and full details. The memory component is up to 2x1024 MB GDDR3 with speeds up to 950MHz in MXM 3.0 boards or up to 800 MHz in MXM 2.0 boards.

An advantage of the GeForce GTX 260M SLI is the integrated PureVideo HD video processor. As a result, it is able to decode/encode H.264-, VC-1-, MPEG2- and WMV9 video material that would have otherwise been processed by the CPU. This ultimately allows the CPU to concentrate more on other tasks and programs simultaneously.

Both chips also support PhysX and CUDA applications. A single GTX 260M can also be used to calculate PhysX effects if supported by the game or application.

HybridPower is a technique to choose between the integrated (if available) and dedicated graphics core for power-saving purposes. So far, this works only in Windows Vista. Up to now, the user had to use a tool to switch between the GPUs. In the near future, Nvidia intends to be able to switch GPUs automatically in the drivers (now known as Optimus Technology, which is not supported by the GTX 260M SLI). GeForceBoost is not supported with this card as there would be no performance gain if one were to combine the integrated GPU with the dedicated 460M SLI.

The current consumption of up to 2x75 = 150 Watts (including the MXM board and VRAM) allows the use of the SLI cards only in laptops with a strong cooling system. Therefore, the GTX 260M SLI can be found only in heavier and larger desktop replacement (DTR) notebooks.

Compared with desktop graphics cards, the performance of the GTX 260M SLI is about on par with the GeForce 9800 GT SLI (600/1500/900).

NVIDIA GeForce GTX 260M

► remove from comparison NVIDIA GeForce GTX 260M

The NVidia GeForce GTX 260M is a high-end graphics card of the 200M series based on the G92b core. Therefore, the 55nm chip is essentially a 9800M GTX with slightly higher clock rates (550/1375/950 vs. 500/1250/800). As a result, the 260M is more similar to the desktop 9800GT than the GTX 260.

As with all native DirectX 10 cards, the GeForce GTX 260M renders 3D images using "Unified Shaders". Dedicated pixel shaders and vertex shaders have been replaced with 112 stream processors in the 260M, which now take over most of the graphics workload. The shader units themselves are also clocked higher (1375 MHz) than the core chip.

In general, the performance of the GTX 260M is somewhat higher than the 9800M GTX due to the higher clock speed. For current DirectX 10 games such as Crysis, World in Conflict, Bioshock or Age of Conan, the 260M is sufficient for gameplay under medium to high detail settings. Meanwhile, older games should be able to run fluently under high resolutions and full details. VRAM can be up to 1024 MB GDDR3 at 950MHz  in MXM 3.0 or 800MHz in MXM 2.0.

The GeForce GTX 260M integrates the PureVideo HD video decoder. The GPU is thus able to assist the CPU in the decoding of H.264-, VC-1-, MPEG2- and WMV9 videos.

HybridPower is a Windows Vista-only technology that allows users to switch between the integrated and dedicated graphics core for power-saving purposes. In the future, Nvidia intends to evolve the software for automatic switching depending on the active application (now known as Optimus). GeForceBoost is not supported with the GTX 260M as there would be no performance gain from combining with the integrated GPU.

The high current consumption of up to 75 Watts (of the entire MXM board) means that the GTX 260M can typically only be found in larger notebooks with loud and powerful cooling systems.

Compared with Desktop graphics cards, the GTX 260M is most similar to the GeForce 9800 GT.

NVIDIA GeForce GTX 285M SLI

► remove from comparison NVIDIA GeForce GTX 285M SLI

The Nvidia GeForce GTX 285M SLI is a graphics solution that combines two Nvidia GeForce GTX 285M with an SLI connection. As not every game supports SLI efficiently, the performance increase compared to a single card is only about 0-40%. The most frequently used technique is Alternate Frame Rendering (AFR), where each card take turns rendering a frame in an alternating manner. Therefore, the SLI solution may suffer from noticeable micro stuttering at frame-rates between 20-30 fps (due to display irregularities between each rendered frame).

Each of the two GeForce GTX 285M is based on the G92b core and is therefore produced in 55nm. It features the full 128 pipelines of the G92b core and is therefore comparable to the desktop 9800M GTX+ and not the desktop GTX 280.

The Nvidia GeForce GTX 285M SLI in laptops with Core 2 Duo CPUs is bundled with the GeForce 9400M G chipset and therefore supports HybridPower (if the manufacturer enables it). With HybridPower, both GTX cards can be disabled and only the chipset graphics core can run, leading to improved battery life (and possibly less fan noise). Modern Core i7 laptops are using an Intel chipset and do not support HybridPower.

Since there are two GTX 285M cards active in SLI, the electrical current consumption and exhumed heat are about twice as much as what a single GTX 285M can produce. Due to the large power and cooling requirements, this SLI combination can only be found in large DTR laptops (like the Alienware M17x).

NVIDIA GeForce GTX 260M SLINVIDIA GeForce GTX 260MNVIDIA GeForce GTX 285M SLI
GeForce GTX 200M Series
GeForce GTX 285M SLI 256 @ 0.58 GHz256 Bit @ 1020 MHz
GeForce GTX 280M SLI 256 @ 0.59 GHz256 Bit @ 950 MHz
GeForce GTX 260M SLI 224 @ 0.55 GHz256 Bit @ 950 MHz
GeForce GTX 285M 128 @ 0.58 GHz256 Bit @ 1020 MHz
GeForce GTX 280M 128 @ 0.59 GHz256 Bit @ 950 MHz
GeForce GTX 260M 112 @ 0.55 GHz256 Bit @ 950 MHz
GeForce GTX 285M SLI 256 @ 0.58 GHz256 Bit @ 1020 MHz
GeForce GTX 280M SLI 256 @ 0.59 GHz256 Bit @ 950 MHz
GeForce GTX 260M SLI 224 @ 0.55 GHz256 Bit @ 950 MHz
GeForce GTX 285M 128 @ 0.58 GHz256 Bit @ 1020 MHz
GeForce GTX 280M 128 @ 0.59 GHz256 Bit @ 950 MHz
GeForce GTX 260M 112 @ 0.55 GHz256 Bit @ 950 MHz
GeForce GTX 285M SLI 256 @ 0.58 GHz256 Bit @ 1020 MHz
GeForce GTX 280M SLI 256 @ 0.59 GHz256 Bit @ 950 MHz
GeForce GTX 260M SLI 224 @ 0.55 GHz256 Bit @ 950 MHz
GeForce GTX 285M 128 @ 0.58 GHz256 Bit @ 1020 MHz
GeForce GTX 280M 128 @ 0.59 GHz256 Bit @ 950 MHz
GeForce GTX 260M 112 @ 0.55 GHz256 Bit @ 950 MHz
CodenameNB9E-GTXN10E-GTN10E-GTX
ArchitectureG9xG9xG9x
Pipelines224 - unified112 - unified256 - unified
Core Speed550 MHz550 MHz576 MHz
Shader Speed1375 MHz1375 MHz1500 MHz
Memory Speed950 MHz950 MHz1020 MHz
Memory Bus Width256 Bit256 Bit256 Bit
Memory TypeGDDR3GDDR3GDDR3
Max. Amount of Memory2048 MB1024 MB2048 (2x1024) MB
Shared Memorynonono
APIDirectX 10, Shader 4.0DirectX 10, Shader 4.0DirectX 10, Shader 4.0
Power Consumption150 Watt75 Watt150 Watt
Transistors1.5 Billion754 Million1.5 Billion
technology55 nm55 nm55 nm
FeaturesHybridPower, PureVideo HD, CUDA, PhysX readyHybridPower, PureVideo HD, CUDA, PhysX readyHybridPower, PureVideo HD, CUDA, PhysX ready
Notebook Sizelargelargelarge
Date of Announcement02.03.2009 02.03.2009 02.03.2009
InformationMXM 3MXM 3MXM 3
Link to Manufacturer Pagehttp://www.nvidia.com/object/product_gef...http://www.nvidia.com/object/product_gef...http://www.nvidia.com/object/product_gef...

Benchmarks

3DMark Vantage
3DM Vant. Perf. total + NVIDIA GeForce GTX 260M SLI
3DMark Vantage - 3DM Vant. Perf. total
8959 Points (7%)
3DM Vant. Perf. total + NVIDIA GeForce GTX 260M
min: 4080     avg: 4953     median: 4901 (4%)     max: 5686 Points
3DM Vant. Perf. total + NVIDIA GeForce GTX 285M SLI
11233 Points (9%)
3DM Vant. Perf. GPU no PhysX + NVIDIA GeForce GTX 260M SLI
3DMark Vantage - 3DM Vant. Perf. GPU no PhysX
8764 Points (7%)
3DM Vant. Perf. GPU no PhysX + NVIDIA GeForce GTX 260M
min: 3840     avg: 4316     median: 4207 (3%)     max: 5058 Points
3DM Vant. Perf. GPU no PhysX + NVIDIA GeForce GTX 285M SLI
10511 Points (8%)
3DMark 2001SE - 3DMark 2001 - Standard
30910 Points (32%)
min: 32699     avg: 34053     median: 34304 (36%)     max: 34905 Points
3DMark 03 - 3DMark 03 - Standard
min: 47633     avg: 49182     median: 49181.5 (26%)     max: 50730 Points
min: 27301     avg: 29794     median: 30595.5 (16%)     max: 30685 Points
3DMark 05 - 3DMark 05 - Standard
min: 12820     avg: 14510     median: 14509.5 (20%)     max: 16199 Points
min: 12669     avg: 14773     median: 15079 (21%)     max: 16611 Points
21611 Points (30%)
3DMark 06 3DMark 06 - Standard 1280x1024 + NVIDIA GeForce GTX 260M SLI
3DMark 06
min: 10794     avg: 11989     median: 11989 (18%)     max: 13184 Points
3DMark 06 - Standard 1280x1024 + NVIDIA GeForce GTX 260M
min: 9458     avg: 10167     median: 10064 (15%)     max: 11209 Points
3DMark 06 - Standard 1280x1024 + NVIDIA GeForce GTX 285M SLI
16608 Points (25%)
3DMark 06 - Score Unknown Settings + NVIDIA GeForce GTX 260M
3DMark 06
10370 Points (16%)
3DMark 06 - Score Unknown Settings + NVIDIA GeForce GTX 285M SLI
16132 Points (24%)
3DMark 06 - Standard 1280x720 + NVIDIA GeForce GTX 260M
3DMark 06
10075 Points (15%)
Windows 7 Experience Index - Win7 Gaming graphics
6.8 Points (86%)
7.3 Points (92%)
Windows 7 Experience Index - Win7 Graphics
6.8 Points (86%)
7.3 Points (92%)
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 260M SLI
Cinebench R10 - Cinebench R10 Shading (32bit)
3995 Points (17%)
Cinebench R10 Shading (32bit) + NVIDIA GeForce GTX 260M
min: 3702     avg: 3966     median: 3917 (17%)     max: 4425 Points
Cinebench R10 Shading (32bit) + NVIDIA GeForce GTX 285M SLI
min: 4418     avg: 4616     median: 4482 (19%)     max: 4949 Points
Cinebench R11.5 Cinebench R11.5 OpenGL 64 Bit + NVIDIA GeForce GTX 260M
Cinebench R11.5 - Cinebench R11.5 OpenGL 64 Bit
28 fps (10%)
Cinebench R11.5 OpenGL 64 Bit + NVIDIA GeForce GTX 285M SLI
min: 29.33     avg: 30.7     median: 30.7 (11%)     max: 32.04 fps

Average Benchmarks NVIDIA GeForce GTX 260M SLI → 100% n=5

Average Benchmarks NVIDIA GeForce GTX 260M → 78% n=5

Average Benchmarks NVIDIA GeForce GTX 285M SLI → 129% n=5

- Range of benchmark values for this graphics card
- Average benchmark values for this graphics card
* Smaller numbers mean a higher performance
1 This benchmark is not used for the average calculation

Game Benchmarks

The following benchmarks stem from our benchmarks of review laptops. The performance depends on the used graphics memory, clock rate, processor, system settings, drivers, and operating systems. So the results don't have to be representative for all laptops with this GPU. For detailed information on the benchmark results, click on the fps number.

Mafia 2

Mafia 2

2010
med. 1024x768
GeForce GTX 260M:
45  fps
high 1360x768
GeForce GTX 260M:
43.8  fps
low 1024x768
GeForce GTX 260M:
154  fps
high 1360x768
GeForce GTX 260M:
47  fps
low 1024x768
GeForce GTX 260M:
79.1  fps
med. 1366x768
GeForce GTX 260M:
54.8  fps
high 1366x768
GeForce GTX 260M:
41.6  fps
GeForce GTX 285M SLI:
81.5  fps
ultra 1920x1080
GeForce GTX 260M:
23.2  fps
GeForce GTX 285M SLI:
50.6  fps
low 800x600
GeForce GTX 260M:
137.4  fps
med. 1024x768
GeForce GTX 260M:
59.1  fps
GeForce GTX 285M SLI:
118.1  fps
high 1366x768
GeForce GTX 260M:
55.4  fps
GeForce GTX 285M SLI:
113.9  fps
ultra 1920x1080
GeForce GTX 260M:
40  fps
GeForce GTX 285M SLI:
84.3  fps
Risen

Risen

2009
low 800x600
GeForce GTX 260M:
51.3 80.3 ~ 66 fps
med. 1024x768
GeForce GTX 260M:
41.3 50.5 ~ 46 fps
GeForce GTX 285M SLI:
103.5  fps
high 1366x768
GeForce GTX 260M:
31.7 36.5 ~ 34 fps
GeForce GTX 285M SLI:
84.7  fps
ultra 1920x1080
GeForce GTX 260M:
26.9  fps
GeForce GTX 285M SLI:
58  fps
Need for Speed Shift

Need for Speed Shift

2009
med. 1024x768
GeForce GTX 260M:
66.5  fps
GeForce GTX 285M SLI:
86.2  fps
high 1366x768
GeForce GTX 260M:
61  fps
GeForce GTX 285M SLI:
85.3  fps
ultra 1920x1080
GeForce GTX 260M:
39.1  fps
GeForce GTX 285M SLI:
79.8  fps
Colin McRae: DIRT 2

Colin McRae: DIRT 2

2009
low 800x600
GeForce GTX 260M:
92  fps
med. 1024x768
GeForce GTX 260M:
79.2  fps
GeForce GTX 285M SLI:
127.1  fps
high 1360x768
GeForce GTX 260M:
61.5  fps
GeForce GTX 285M SLI:
103.7  fps
ultra 1920x1080
GeForce GTX 260M:
35.3  fps
GeForce GTX 285M SLI:
69.9  fps
Anno 1404

Anno 1404

2009
low 1024x768
GeForce GTX 260M:
125.2 133 ~ 129 fps
ultra 1280x1024
GeForce GTX 260M:
36.2 39 44 49.5 ~ 42 fps
GeForce GTX 285M SLI:
89.4  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
GeForce GTX 260M:
63.8 65 67.4 73.4 77.4 ~ 69 fps
GeForce GTX 285M SLI:
127.5  fps
ultra 1920x1080
GeForce GTX 260M:
41.8  fps
GeForce GTX 285M SLI:
87.7  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
100%
GeForce GTX 260M SLI:
102  fps
106%
GeForce GTX 260M:
92 123.7 ~ 108 fps
med. 1024x768
100%
GeForce GTX 260M SLI:
64  fps
98%
GeForce GTX 260M:
56 57.2 76.9 ~ 63 fps
116%
GeForce GTX 285M SLI:
74.2  fps
high 1024x768
100%
GeForce GTX 260M SLI:
51  fps
75%
GeForce GTX 260M:
31 38 38.4 39.3 41.9 ~ 38 fps
122%
GeForce GTX 285M SLI:
62  fps
ultra 1920x1080
GeForce GTX 260M:
12.2  fps
GeForce GTX 285M SLI:
26.9  fps
Crysis - CPU Benchmark

Crysis - CPU Benchmark

2007
low 1024x768
100%
GeForce GTX 260M SLI:
132  fps
91%
GeForce GTX 260M:
110 129.5 ~ 120 fps
med. 1024x768
100%
GeForce GTX 260M SLI:
65  fps
92%
GeForce GTX 260M:
49 52.6 76.9 ~ 60 fps
114%
GeForce GTX 285M SLI:
73.9  fps
high 1024x768
100%
GeForce GTX 260M SLI:
52  fps
69%
GeForce GTX 260M:
30.7 35.5 37 37 39.2 ~ 36 fps
114%
GeForce GTX 285M SLI:
59.3  fps
ultra 1920x1080
GeForce GTX 260M:
11.5  fps
GeForce GTX 285M SLI:
24.9  fps
World in Conflict - Benchmark

World in Conflict - Benchmark

2007
med. 1024x768
GeForce GTX 260M:
47 72 ~ 60 fps
high 1024x768
GeForce GTX 260M:
38 42 ~ 40 fps
Call of Juarez Benchmark

Call of Juarez Benchmark

2006
high 1024x768
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 260M SLI → 100%

Average Gaming 30-70 fps → 100%

Average Gaming NVIDIA GeForce GTX 260M → 89%

Average Gaming 30-70 fps → 84%

Average Gaming NVIDIA GeForce GTX 285M SLI → 116%

Average Gaming 30-70 fps → 118%

For more games that might be playable and a list of all games and graphics cards visit our Gaming List

v1.17
log 03. 08:14:19

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

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

#2 checking url part for id 1643 +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 Wed, 29 Jun 2022 17:25:55 +0200 +0s ... 0s

#5 linkCache_getLink using $NBC_LINKCACHE +0.047s ... 0.048s

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

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

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

#9 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.05s

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

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

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

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

#14 composed specs +0s ... 0.05s

#15 did output specs +0s ... 0.05s

#16 start showIntegratedCPUs +0s ... 0.05s

#17 getting avg benchmarks for device 1229 +0.047s ... 0.096s

#18 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.097s

#19 got single benchmarks 1229 +0.005s ... 0.102s

#20 getting avg benchmarks for device 1111 +0s ... 0.102s

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

#22 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.104s

#23 got single benchmarks 1111 +0.019s ... 0.123s

#24 getting avg benchmarks for device 1643 +0s ... 0.124s

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

#26 got single benchmarks 1643 +0.007s ... 0.131s

#27 got avg benchmarks for devices +0s ... 0.131s

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

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

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

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

#32 linkCache_getLink no uid found +0.001s ... 0.133s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#82 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.139s

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

#84 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.14s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#100 linkCache_getLink no uid found +0s ... 0.142s

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

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

#103 min, max, avg, median took s +0.001s ... 0.142s

#104 before gaming benchmark output +0s ... 0.142s

#105 Got 138 rows for game benchmarks. +0.01s ... 0.153s

#106 composed SQL query for gamebenchmarks +0s ... 0.153s

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

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

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

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

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

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

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

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

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

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

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

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

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

#120 got data and put it in $dataArray +0.006s ... 0.159s

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

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

#123 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.161s

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

#125 linkCache_getLink no uid found +0.001s ... 0.162s

#126 linkCache_getLink no uid found +0s ... 0.162s

#127 linkCache_getLink no uid found +0s ... 0.162s

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

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

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

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

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

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

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

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

#136 linkCache_getLink no uid found +0s ... 0.163s

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

#138 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.164s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#154 linkCache_getLink no uid found +0.001s ... 0.166s

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

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

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

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

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

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

#161 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.168s

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

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

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

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

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

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

#168 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.17s

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

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

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

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

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

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

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

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

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

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

#179 linkCache_getLink no uid found +0s ... 0.17s

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

#181 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.171s

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

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

#184 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.172s

#185 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.172s

#186 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.172s

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

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

#189 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.172s

#190 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.173s

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

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

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

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

#195 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.173s

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

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

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

#199 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.174s

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

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

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

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

#204 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.174s

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

#206 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.175s

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

#208 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.176s

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

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

#211 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.176s

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

#213 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.176s

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

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

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

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

#218 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.176s

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

#220 linkCache_getLink no uid found +0s ... 0.176s

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

#222 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.177s

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

#224 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.177s

#225 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.177s

#226 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.177s

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

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

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

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

#231 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.177s

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

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

#234 linkCache_getLink no uid found +0s ... 0.177s

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

#236 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.178s

#237 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.178s

#238 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.178s

#239 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.178s

#240 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.179s

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

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

#243 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.182s

#244 benchmarks composed for output. +0.003s ... 0.185s

#245 calculated avg scores. +0s ... 0.185s

#246 return log +0.001s ... 0.186s

Please share our article, every link counts!
> Notebook / Laptop Reviews and News > Benchmarks / Tech > Graphics Card Comparison - Head 2 Head
Redaktion, 2017-09- 8 (Update: 2017-09-11)