Notebookcheck Logo

NVIDIA Quadro 4000M vs NVIDIA Quadro 5010M

NVIDIA Quadro 4000M

► remove from comparison NVIDIA Quadro 4000M

The NVIDIA Quadro 4000M is a professional workstation graphics card based on the Fermi architecture (or more specifically, probably the GF104). Unlike the 5010M, the 4000M does not support ECC memory and dual-precision (DP) floating point calculations.

The Quadro series offers certified drivers that are optimized for stability and performance in professional applications such as CAD or DCC. As a result, multiple scientific or business disciplines can make use of the workstation GPU. The OpenGL performance, for example, should be significantly better than consumer-oriented GeForce graphics cards of similar specifications.

The shader / CUDA cores can be accessed using DirectX 11 or OpenGL 4.1 for graphics rendering or DirectCompute, OpenCL, AXE, and CUDA for general purpose calculations. Due to the new Fermi core, the 4000M should offer higher performance in general purpose calculations compared to its predecessors.

Furthermore, the Nvidia Quadro 4000M is compatible with 3D Vision Pro, a new software solution by Nvidia for stereoscopic output.

The 4000M supports Nvidia Optimus in order to automatically switch between the integrated graphics card and the Quadro for power-saving purposes. Whether or not this feature is supported on a laptop, however, is dependent on the laptop manufacturer.

Similar to the GeForce GTX 480M, the Quadro 4000M is specified at 100 Watt TDP and is therefore only found in large laptops such as the Clevo D901F.

NVIDIA Quadro 5010M

► remove from comparison NVIDIA Quadro 5010M

The NVIDIA Quadro 5010M is a professional workstation graphics card based on the Fermi architecture (GF100 chip). Therefore, the 5010M is closely related to the  consumer GeForce GTX 480M. The Quadro 5010M is the successor to the Quadro 5000M and also offers ECC RAM and double-precision floating point cores.

The Quadro series offers certified drivers that are optimized for stability and performance in professional applications like CAD, DCC, medicine, or visualisation areas. The OpenGL performance, for example, should be significantly better than GeForce graphics cards with similar specifications.

The shader / CUDA cores can be accessed using DirectX 11 or OpenGL 4.1 for graphics rendering and DirectCompute, OpenCL, AXE, and CUDA for general purpose calculations. Due to the new Fermi architecture, the 5010M should offer higher levels of performance in general purpose calculations compared to its predecessors.

Furthermore, the Nvidia Quadro 5010M is compatible with the new stereoscopic solution by Nvidia called 3D Vision Pro.

To automatically switch between the integrated graphics card and the Quadro, the 5010M supports Nvidia Optimus. Note, however, that whether this feature is integrated or not depends on the notebook manufacturer.

Similar to the GeForce GTX 480M, the Quadro 5010M is specified at 100 Watt TDP. As a result, only very large laptops, such as the Clevo D901F, are able to house this high-end card.

At the time of arrival (Feb. 2011), the Quadro 5010M succeeds the older Quadrio FX 5000M as the fastest professional workstation graphic card for laptops.

NVIDIA Quadro 4000MNVIDIA Quadro 5010M
Quadro M Series
Quadro M5500 compare 2048 @ 1.14 - 1.14 GHz256 Bit @ 6606 MHz
Quadro M5000M compare 1536 @ 0.96 - 1.05 GHz256 Bit @ 5000 MHz
Quadro M4000M compare 1280 @ 0.98 - 1.01 GHz256 Bit @ 5012 MHz
Quadro M3000M compare 1024 @ 1.05 GHz256 Bit @ 5000 MHz
Quadro M2200 compare 1024 @ 0.69 - 1.04 GHz128 Bit @ 5508 MHz
Quadro M1200 compare 640 @ 0.99 - 1.15 GHz128 Bit @ 5000 MHz
Quadro M2000M compare 640 @ 1.04 - 1.2 GHz128 Bit @ 5000 MHz
Quadro M1000M compare 512 @ 0.99 - 1.07 GHz128 Bit @ 5000 MHz
Quadro M620 compare 512 @ 1.02 GHz128 Bit @ 5012 MHz
Quadro 5010M 384 @ 0.45 GHz256 Bit @ 1300 MHz
Quadro 4000M 336 @ 0.48 GHz256 Bit @ 1200 MHz
Quadro M520 compare 384 @ 0.76 - 1.02 GHz64 Bit
Quadro M600M compare 384 @ 0.84 - 0.88 GHz128 Bit @ 5012 MHz
Quadro M500M compare 384 @ 1.03 - 1.12 GHz64 Bit @ 4004 MHz
Quadro 5000M compare 320 @ 0.41 GHz256 Bit @ 1200 MHz
Quadro 3000M compare 240 @ 0.45 GHz256 Bit @ 625 MHz
Quadro 2000M compare 192 @ 0.55 GHz128 Bit @ 900 MHz
Quadro 1000M compare 96 @ 0.7 GHz128 Bit @ 900 MHz
Quadro M5500 compare 2048 @ 1.14 - 1.14 GHz256 Bit @ 6606 MHz
Quadro M5000M compare 1536 @ 0.96 - 1.05 GHz256 Bit @ 5000 MHz
Quadro M4000M compare 1280 @ 0.98 - 1.01 GHz256 Bit @ 5012 MHz
Quadro M3000M compare 1024 @ 1.05 GHz256 Bit @ 5000 MHz
Quadro M2200 compare 1024 @ 0.69 - 1.04 GHz128 Bit @ 5508 MHz
Quadro M1200 compare 640 @ 0.99 - 1.15 GHz128 Bit @ 5000 MHz
Quadro M2000M compare 640 @ 1.04 - 1.2 GHz128 Bit @ 5000 MHz
Quadro M1000M compare 512 @ 0.99 - 1.07 GHz128 Bit @ 5000 MHz
Quadro M620 compare 512 @ 1.02 GHz128 Bit @ 5012 MHz
Quadro 5010M 384 @ 0.45 GHz256 Bit @ 1300 MHz
Quadro 4000M 336 @ 0.48 GHz256 Bit @ 1200 MHz
Quadro M520 compare 384 @ 0.76 - 1.02 GHz64 Bit
Quadro M600M compare 384 @ 0.84 - 0.88 GHz128 Bit @ 5012 MHz
Quadro M500M compare 384 @ 1.03 - 1.12 GHz64 Bit @ 4004 MHz
Quadro 5000M compare 320 @ 0.41 GHz256 Bit @ 1200 MHz
Quadro 3000M compare 240 @ 0.45 GHz256 Bit @ 625 MHz
Quadro 2000M compare 192 @ 0.55 GHz128 Bit @ 900 MHz
Quadro 1000M compare 96 @ 0.7 GHz128 Bit @ 900 MHz
CodenameFermiN12E-Q5
ArchitectureFermiFermi
Pipelines336 - unified384 - unified
Core Speed475 MHz450 MHz
Shader Speed950 MHz900 MHz
Memory Speed1200 MHz1300 MHz
Memory Bus Width256 Bit256 Bit
Memory TypeGDDR5GDDR5 ECC
Max. Amount of Memory2048 MB4 GB
Shared Memorynono
APIDirectX 11, Shader 5.0DirectX 11, Shader 5.0
Power Consumption100 Watt100 Watt
technology40 nm40 nm
FeaturesOpenGl 4.1, FP32OpenGl 4.1, ECC Memory, FP64 IEEE 754
Notebook Sizelargelarge
Date of Announcement22.02.2011 22.02.2011
Link to Manufacturer Pagehttp://www.nvidia.com/object/quadro-mobi...http://www.nvidia.com/object/quadro-mobi...
Transistors3 Billion

Benchmarks

3DMark 11 - 3DM11 Performance Score
min: 2229     avg: 2335     median: 2334.5 (5%)     max: 2440 Points
min: 3032     avg: 3066     median: 3066 (6%)     max: 3100 Points
3DMark 11 - 3DM11 Performance GPU
min: 2025     avg: 2092     median: 2092 (3%)     max: 2159 Points
2693 Points (4%)
3DMark Vantage
3DM Vant. Perf. total + NVIDIA Quadro 4000M
3DMark Vantage - 3DM Vant. Perf. total
10722 Points (3%)
3DM Vant. Perf. total + NVIDIA Quadro 5010M
12991 Points (4%)
3DM Vant. Perf. GPU no PhysX + NVIDIA Quadro 4000M
3DMark Vantage - 3DM Vant. Perf. GPU no PhysX
9184 Points (6%)
3DM Vant. Perf. GPU no PhysX + NVIDIA Quadro 5010M
11047 Points (7%)
3DMark 03 - 3DMark 03 - Standard
52873 Points (28%)
3DMark 05 - 3DMark 05 - Standard
24769 Points (29%)
3DMark 06 3DMark 06 - Standard 1280x1024 + NVIDIA Quadro 4000M
3DMark 06
17727 Points (26%)
3DMark 06 - Standard 1280x1024 + NVIDIA Quadro 5010M
min: 18617     avg: 19544     median: 19036 (28%)     max: 20979 Points
Unigine Heaven 2.1 - Heaven 2.1 high
31.4 fps (6%)
41.7 fps (8%)
SPECviewperf 11
specvp11 snx-01 + NVIDIA Quadro 4000M
SPECviewperf 11 - specvp11 snx-01
26.4 fps (19%)
specvp11 snx-01 + NVIDIA Quadro 5010M
min: 34.9     avg: 38.2     median: 38.2 (27%)     max: 41.4 fps
specvp11 tcvis-02 + NVIDIA Quadro 4000M
SPECviewperf 11 - specvp11 tcvis-02
29.2 fps (49%)
specvp11 tcvis-02 + NVIDIA Quadro 5010M
min: 37.6     avg: 39.8     median: 39.8 (67%)     max: 41.9 fps
specvp11 sw-02 + NVIDIA Quadro 4000M
SPECviewperf 11 - specvp11 sw-02
39.1 fps (47%)
specvp11 sw-02 + NVIDIA Quadro 5010M
min: 37.93     avg: 46.1     median: 46.1 (56%)     max: 54.2 fps
specvp11 proe-05 + NVIDIA Quadro 4000M
SPECviewperf 11 - specvp11 proe-05
10.6 fps (44%)
specvp11 proe-05 + NVIDIA Quadro 5010M
min: 7.99     avg: 8.8     median: 8.8 (37%)     max: 9.7 fps
specvp11 maya-03 + NVIDIA Quadro 4000M
SPECviewperf 11 - specvp11 maya-03
51.4 fps (39%)
specvp11 maya-03 + NVIDIA Quadro 5010M
min: 53.6     avg: 72.4     median: 72.4 (55%)     max: 91.1 fps
specvp11 lightwave-01 + NVIDIA Quadro 4000M
SPECviewperf 11 - specvp11 lightwave-01
42.1 fps (45%)
specvp11 lightwave-01 + NVIDIA Quadro 5010M
min: 40.01     avg: 47.5     median: 47.5 (51%)     max: 54.9 fps
specvp11 ensight-04 + NVIDIA Quadro 4000M
SPECviewperf 11 - specvp11 ensight-04
24.9 fps (12%)
specvp11 ensight-04 + NVIDIA Quadro 5010M
min: 36.73     avg: 37.9     median: 37.9 (18%)     max: 39.1 fps
specvp11 catia-03 + NVIDIA Quadro 4000M
SPECviewperf 11 - specvp11 catia-03
36.5 fps (44%)
specvp11 catia-03 + NVIDIA Quadro 5010M
min: 33.89     avg: 38.2     median: 38.1 (46%)     max: 42.4 fps
Windows 7 Experience Index - Win7 Gaming graphics
7.1 Points (90%)
7.5 Points (95%)
Windows 7 Experience Index - Win7 Graphics
7.1 Points (90%)
7.5 Points (95%)
Cinebench R10 Cinebench R10 Shading (32bit) + NVIDIA Quadro 4000M
Cinebench R10 - Cinebench R10 Shading (32bit)
6638 Points (5%)
Cinebench R10 Shading (32bit) + NVIDIA Quadro 5010M
6620 Points (5%)
Cinebench R11.5 Cinebench R11.5 OpenGL 64 Bit + NVIDIA Quadro 4000M
Cinebench R11.5 - Cinebench R11.5 OpenGL 64 Bit
46 fps (17%)
Cinebench R11.5 OpenGL 64 Bit + NVIDIA Quadro 5010M
min: 65.1     avg: 67.5     median: 67.5 (25%)     max: 69.9 fps

Average Benchmarks NVIDIA Quadro 4000M → 100% n=18

Average Benchmarks NVIDIA Quadro 5010M → 122% n=18

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

Dirt 3

Dirt 3

2011
high 1360x768
Quadro 5010M:
105.4 fps  fps
ultra 1920x1080
Quadro 5010M:
35.3 fps  fps
Crysis 2

Crysis 2

2011
high 1366x768
Quadro 5010M:
81.6 fps  fps
ultra 1920x1080
Quadro 5010M:
28.2 fps  fps
high 1360x768
Quadro 5010M:
105  fps
ultra 1920x1080
Quadro 5010M:
72.8  fps
Fifa 11

Fifa 11

2010
high 1360x768
Quadro 5010M:
268.6  fps
ultra 1920x1080
Quadro 5010M:
162.3  fps
Mafia 2

Mafia 2

2010
high 1360x768
Quadro 5010M:
86.6  fps
ultra 1920x1080
Quadro 5010M:
51.9  fps
low 1024x768
100%
Quadro 4000M:
180  fps
med. 1360x768
100%
Quadro 4000M:
112  fps
high 1360x768
100%
Quadro 4000M:
79  fps
125%
Quadro 5010M:
98.4  fps
ultra 1920x1080
100%
Quadro 4000M:
71  fps
74%
Quadro 5010M:
52.7  fps
high 1600x900
Quadro 5010M:
37.9  fps
ultra 1920x1080
Quadro 5010M:
14.6  fps
high 1366x768
Quadro 5010M:
88.9  fps
ultra 1920x1080
Quadro 5010M:
45.3  fps
high 1366x768
Quadro 5010M:
93.4  fps
ultra 1920x1080
Quadro 5010M:
62.5  fps
Risen

Risen

2009
high 1366x768
Quadro 5010M:
64.3  fps
ultra 1920x1080
Quadro 5010M:
41.9  fps
Resident Evil 5

Resident Evil 5

2009
high 1360x768
Quadro 5010M:
120.6  fps
ultra 1920x1080
Quadro 5010M:
73.3  fps
Need for Speed Shift

Need for Speed Shift

2009
high 1366x768
Quadro 5010M:
108.5  fps
ultra 1920x1080
Quadro 5010M:
67  fps
Anno 1404

Anno 1404

2009
low 1024x768
100%
Quadro 4000M:
173  fps
ultra 1280x1024
100%
Quadro 4000M:
62  fps
Sims 3

Sims 3

2009
low 800x600
100%
Quadro 4000M:
279  fps
med. 1024x768
100%
Quadro 4000M:
165  fps
high 1280x1024
100%
Quadro 4000M:
79  fps
Racedriver: GRID

Racedriver: GRID

2008
low 800x600
100%
Quadro 4000M:
188  fps
med. 1024x768
100%
Quadro 4000M:
148  fps
high 1280x1024
100%
Quadro 4000M:
117  fps

Average Gaming NVIDIA Quadro 4000M → 100%

Average Gaming 30-70 fps → 100%

Average Gaming NVIDIA Quadro 5010M → 99%

Average Gaming 30-70 fps → 74%

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.18
log 30. 14:11:09

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

#1 checking url part for id 2429 +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, 27 Sep 2022 17:27:11 +0200 +0s ... 0s

#4 linkCache_getLink using $NBC_LINKCACHE +0.053s ... 0.054s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#25 getting avg benchmarks for device 2431 +0.025s ... 0.084s

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

#27 got single benchmarks 2431 +0.006s ... 0.091s

#28 getting avg benchmarks for device 2429 +0s ... 0.091s

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

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

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

#32 got single benchmarks 2429 +0.006s ... 0.097s

#33 got avg benchmarks for devices +0s ... 0.097s

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

#35 linkCache_getLink no uid found +0.001s ... 0.098s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#63 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.104s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#84 min, max, avg, median took s +0s ... 0.108s

#85 before gaming benchmark output +0s ... 0.108s

#86 Got 36 rows for game benchmarks. +0.005s ... 0.114s

#87 composed SQL query for gamebenchmarks +0s ... 0.114s

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

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

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

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

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

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

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

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

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

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

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

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

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

#101 got data and put it in $dataArray +0.002s ... 0.116s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#138 benchmarks composed for output. +0s ... 0.132s

#139 calculated avg scores. +0s ... 0.132s

#140 linkCache_getLink using $NBC_LINKCACHE +0.048s ... 0.181s

#141 return log +0.002s ... 0.183s

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