Notebookcheck Logo
, , , , , ,
search relation.
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
 

NVIDIA GeForce GTX 260M SLI vs NVIDIA GeForce GTX 280M

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 280M

► remove from comparison NVIDIA GeForce GTX 280M

The NVidia GeForce GTX 280M is a high-end graphics card as part of the 200M series and is based on the G92b core (Desktop GeForce 9800 GTX+). Therefore, it is actually more related to the GeForce 9800 GTX+, both performance-wise and architecturally, than to the GTX 280. The chip is produced in 55nm with all 128 pipelines enabled, as opposed to the GT 9800M with only 112 pipelines produced in a 65nm process.

Hybrid Power makes an appearance on the GTX 280M as well, but with much improved performance. Switch times on the graphics card now completes in just a fraction of a second, compared to a full 7 seconds on the 9800M GTX,

As with all DirectX 10 graphics cards, the GeForce GTX 280M renders 3D images using "Unified Shaders". Dedicated pixel and vertex shaders of yesteryear are gone in favor of 128 stream processors running at 1250MHz on the GTX 280M.  The stream processors handle all of the workload that would have otherwise been processed by pixel or vertex shaders. VRAM can be up to 1024 MB GDDR3 clocked at either 800MHz (on MXM2 boards) or 950MHz (on MXM3 boards).

Due to the full 128 shader cores, the GTX 280M is about 10-25% faster than the older 9800M GTX and slightly faster than the 260M. Compared to the performance of the Mobility Radeon HD 4870, the GTX 280M is about equal in synthetic benchmarks, if not slightly lower. The Nvidia card, however, has proven to be slightly faster in games, so the GTX 280M can therefore be rated more highly in terms of real-life performance. Specifically, games with PhysX support (e.g., Mirrors Edge) can have significant performance advantages if PhysX effects are enabled. 

Another feature of the GeForce GTX 280M is the integrated PureVideo HD video processor. The card is able to assist the CPU in decoding of H.264-, VC-1-, MPEG2- and WMV9 video material.

HybridPower is a Windows Vista-only technique used to switch between the integrated (only with Nvidia chipset) and dedicated graphics cores for power-saving purposes. Eventually, Nvidia will have its future chips switch automatically between dedicated or integrated through drivers (now known as Optimus Technology). GeForceBoost is not supported with this card, as there would be no performance gain from combining the integrated GPU with the discrete video card.

A high power consumption of up to 75 Watts (including the VRAM and MXM board) means that only large notebooks with powerful (and possibly loud) cooling systems can run the GTX 280M.

The newer GTX 285M is based on the same core as the GTX 280M, but with only slightly altered clock rates. As a result, the performance of the GeForce GTX285M is very similar to the GTX 280M.

Compared with Desktop graphic cards, the performance can be considered somewhere in between the 9800 GT and the 9800 GTX, the latter of which has considerably higher clock rates at 675/1675/1100MHz.

NVIDIA GeForce GTX 260M SLINVIDIA GeForce GTX 280M
GeForce GTX 200M Series
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 224 @ 0.55 GHz256 Bit @ 950 MHz
GeForce GTX 285M compare 128 @ 0.58 GHz256 Bit @ 1020 MHz
GeForce GTX 280M 128 @ 0.59 GHz256 Bit @ 950 MHz
GeForce GTX 260M compare 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 224 @ 0.55 GHz256 Bit @ 950 MHz
GeForce GTX 285M compare 128 @ 0.58 GHz256 Bit @ 1020 MHz
GeForce GTX 280M 128 @ 0.59 GHz256 Bit @ 950 MHz
GeForce GTX 260M compare 112 @ 0.55 GHz256 Bit @ 950 MHz
CodenameNB9E-GTXN10E-GTX
ArchitectureG9xG9x
Pipelines224 - unified128 - unified
Core Speed550 MHz585 MHz
Shader Speed1375 MHz1463 MHz
Memory Speed950 MHz950 MHz
Memory Bus Width256 Bit256 Bit
Memory TypeGDDR3GDDR3
Max. Amount of Memory2048 MB1024 MB
Shared Memorynono
APIDirectX 10, Shader 4.0DirectX 10, Shader 4.0
Power Consumption150 Watt
Transistors1.5 Billion754 Million
technology55 nm55 nm
FeaturesHybridPower, PureVideo HD, CUDA, PhysX readyHybridPower, PureVideo HD, CUDA, PhysX ready
Notebook Sizelargelarge
Date of Announcement02.03.2009 02.03.2009
InformationMXM 3MXM 3
Link to Manufacturer Pagehttp://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 280M
min: 5314     avg: 6328     median: 6672 (6%)     max: 6779 Points
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 280M
min: 5071     avg: 5243     median: 5257.5 (4%)     max: 5319 Points
3DMark 2001SE - 3DMark 2001 - Standard
30910 Points (32%)
min: 36607     avg: 38714     median: 38780 (40%)     max: 40754 Points
3DMark 03 - 3DMark 03 - Standard
min: 47633     avg: 49182     median: 49181.5 (26%)     max: 50730 Points
min: 34632     avg: 35749     median: 35748.5 (19%)     max: 36865 Points
3DMark 05 - 3DMark 05 - Standard
min: 12820     avg: 14510     median: 14509.5 (20%)     max: 16199 Points
min: 16800     avg: 18414     median: 18669 (26%)     max: 20713 Points
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 280M
min: 11767     avg: 12569     median: 12551 (19%)     max: 13652 Points
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 280M
min: 4111     avg: 5505     median: 5276.5 (22%)     max: 7845 Points

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

Average Benchmarks NVIDIA GeForce GTX 280M → 100% n=7

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

Anno 1404

Anno 1404

2009
low 1024x768
GeForce GTX 280M:
100  fps
ultra 1280x1024
GeForce GTX 280M:
40 51.5 52.7 ~ 48 fps
F.E.A.R. 2

F.E.A.R. 2

2009
high 1280x1024
GeForce GTX 280M:
82.5 86.1 91 ~ 87 fps
GTA IV - Grand Theft Auto

GTA IV - Grand Theft Auto

2008
low 800x600
GeForce GTX 280M:
48 55.7 63.9 65.3 ~ 58 fps
med. 1024x768
GeForce GTX 280M:
47 53.9 55.7 56.3 ~ 53 fps
high 1280x1024
GeForce GTX 280M:
33 38.4 39.3 41.5 ~ 38 fps
Left 4 Dead

Left 4 Dead

2008
high 1024x768
GeForce GTX 280M:
104 121.2 131.5 ~ 119 fps
Far Cry 2

Far Cry 2

2008
low 640x480
GeForce GTX 280M:
98  fps
high 1024x768
GeForce GTX 280M:
62  fps
Crysis Warhead

Crysis Warhead

2008
low 800x600
GeForce GTX 280M:
76  fps
ultra 1024x768
GeForce GTX 280M:
17  fps
Racedriver: GRID

Racedriver: GRID

2008
high 1280x1024
GeForce GTX 280M:
72.8  fps
Call of Duty 4 - Modern Warfare

Call of Duty 4 - Modern Warfare

2007
high 1280x1024
GeForce GTX 280M:
75 78.8 117.5 ~ 90 fps
Supreme Commander - FA Bench

Supreme Commander - FA Bench

2007
med. 1024x768
GeForce GTX 280M:
54.6 54.9 56 ~ 55 fps
high 1024x768
GeForce GTX 280M:
45 45.9 46.1 47.3 ~ 46 fps
Crysis - GPU Benchmark

Crysis - GPU Benchmark

2007
low 1024x768
100%
GeForce GTX 260M SLI:
102  fps
120%
GeForce GTX 280M:
106 115.4 128.6 138.9 ~ 122 fps
med. 1024x768
100%
GeForce GTX 260M SLI:
64  fps
102%
GeForce GTX 280M:
60.9 65.9 66 67 ~ 65 fps
high 1024x768
100%
GeForce GTX 260M SLI:
51  fps
88%
GeForce GTX 280M:
43.1 44 45 45.1 48.6 ~ 45 fps
Crysis - CPU Benchmark

Crysis - CPU Benchmark

2007
low 1024x768
100%
GeForce GTX 260M SLI:
132  fps
80%
GeForce GTX 280M:
95.2 102.1 117.1 ~ 105 fps
med. 1024x768
100%
GeForce GTX 260M SLI:
65  fps
103%
GeForce GTX 280M:
61.2 66.2 72.4 ~ 67 fps
high 1024x768
100%
GeForce GTX 260M SLI:
52  fps
87%
GeForce GTX 280M:
41.2 43.8 47.3 49.5 ~ 45 fps
World in Conflict - Benchmark

World in Conflict - Benchmark

2007
med. 1024x768
GeForce GTX 280M:
77  fps
high 1024x768
GeForce GTX 280M:
46  fps
Call of Juarez Benchmark

Call of Juarez Benchmark

2006
high 1024x768
GeForce GTX 280M:
29.3 33 33.1 ~ 32 fps
Half Life 2 - Lost Coast Benchmark

Half Life 2 - Lost Coast Benchmark

2005
high 1024x768
GeForce GTX 280M:
144  fps
Counter-Strike Source

Counter-Strike Source

2004
high 1024x768
GeForce GTX 280M:
265  fps
Doom 3

Doom 3

2004
low 640x480
GeForce GTX 280M:
161  fps
ultra 1024x768
GeForce GTX 280M:
160  fps
Quake 3 Arena - Timedemo

Quake 3 Arena - Timedemo

1999
high 1024x768
GeForce GTX 280M:
695  fps

Average Gaming NVIDIA GeForce GTX 260M SLI → 100%

Average Gaming 30-70 fps → 100%

Average Gaming NVIDIA GeForce GTX 280M → 96%

Average Gaming 30-70 fps → 95%

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

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:29:16

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

#1 checking url part for id 1110 +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 Wed, 25 May 2022 17:25:23 +0200 +0s ... 0s

#4 linkCache_getLink using $NBC_LINKCACHE +0.049s ... 0.05s

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

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

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

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

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

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

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

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

#13 getting avg benchmarks for device 1229 +0.028s ... 0.08s

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

#15 got single benchmarks 1229 +0.004s ... 0.085s

#16 getting avg benchmarks for device 1110 +0s ... 0.085s

#17 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.086s

#18 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.088s

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

#20 got single benchmarks 1110 +0.016s ... 0.104s

#21 got avg benchmarks for devices +0s ... 0.105s

#22 linkCache_getLink no uid found +0s ... 0.105s

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

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

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

#26 linkCache_getLink no uid found +0s ... 0.106s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#48 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.108s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#69 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.109s

#70 min, max, avg, median took s +0s ... 0.109s

#71 before gaming benchmark output +0s ... 0.109s

#72 Got 76 rows for game benchmarks. +0.005s ... 0.115s

#73 composed SQL query for gamebenchmarks +0s ... 0.115s

#74 got data and put it in $dataArray +0.003s ... 0.117s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#94 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.121s

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

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

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

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

#99 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.123s

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

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

#102 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.125s

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

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

#105 linkCache_getLink no uid found +0.001s ... 0.126s

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

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

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

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

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

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

#112 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.126s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#141 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.132s

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

#143 benchmarks composed for output. +0.001s ... 0.133s

#144 calculated avg scores. +0s ... 0.133s

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

#146 return log +0.002s ... 0.136s

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)