Notebookcheck Logo

NVIDIA Quadro K510M vs NVIDIA Quadro K4000M

NVIDIA Quadro K510M

► remove from comparison NVIDIA Quadro K510M

The NVIDIA Quadro K510M is a DirectX 11 and OpenGL 4.3 compatible graphics card for affordable mobile workstations. It is a Kepler-based GPU built on the GK107 chip with 192 out of 384 shader cores activated and is manufactured in 28nm at TSMC. The Quadro K510M is built for the Intel Shark Bay generation (Haswell) and is a successor to the Quadro K500M (Chief River platform). As a new feature, PCIe 3.0 is supported for the first time. The K510M usually comes with 1 GB GDDR5 VRAM clocked at 600 MHz (2400 MHz effective, 19.2 GB/s). 

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

Architecture

The Kepler architecture is the successor to the Fermi architecture that first appeared in laptops with the GeForce 400M series. The GK107 Kepler core offers two shader blocks, called SMX, that are clocked at the same speed as the central core. In the K510M, only one block is active leading to the 192 CUDA cores. Although more shader cores are available in the Kepler architecture as compared to the Fermi design, the Kepler shaders are still expected to be up to twice as power efficient. However, due to the missing hot clock of the shader domain, two shaders of a Kepler chip offer similar performance to just one shader of a Fermi chip (as the latter is clocked twice as fast).

Performance

The performance should be clearly above the old Quadro K500M, but somewhat below the higher clocked Quadro K610M. This would place the K510M between the consumer GPUs GeForce 710M and GT 720M. However, the exact core clock has not yet been confirmed. Nevertheless, most demanding games of 2013 will run fluently only in low detail settings.

Features

The improved feature set now includes support for up to 4 active displays. Furthermore, high resolution monitors of up to 3840 x 2160 pixels can now be connected using DisplayPort 1.2 or HDMI 1.4a if available. HD-Audio codecs, such as Dolby TrueHD and DTS-HD, can be transmitted via bitstream mode through the HDMI port. However, as most laptops will feature Optimus, the integrated GPU will likely have direct control over the display ports and may limit the feature set available by the Nvidia Kepler cards. Please note: The K510M does not supprt 3D Vision Pro.

Using CUDA or OpenCL 1.2, the cores of the Quadro K510M can be used for general calculations.

The 5th generation PureVideo HD video processor (VP5) is also integrated in the GK107 core and offers hardware decoding of HD videos. Common codecs such as MPEG-1/2, MPEG-4 ASP, H.264 and VC1/WMV9 are fully supported up to 4K resolutions while VC1 and MPEG-4 are supported up to 1080p. Two streams can be decoded in parallel for features such as Picture-in-Picture. Another novelty is the inclusion of a dedicated video encoding engine similar to Intel QuickSync that can be accessed by the NVENC API.

The power consumption of the Quadro K510M is rated at a TGP of 30 W including the board and memory components. Therefore, the card is suited for medium-sized notebooks with 15-inch displays or greater.

NVIDIA Quadro K4000M

► remove from comparison NVIDIA Quadro K4000M

The NVIDIA Quadro K4000M is a high-end, DirectX 11.1 compatible graphics card for mobile workstations. It is a Kepler-based GPU built on the GK104 chip (but using only 960 shader cores) and is manufactured in 28nm at TSMC. The Quadro K4000M is built for the Intel Chief River generation (Ivy Bridge) and is the successor to the Fermi-based Quadro 4000M (Huron River platform).

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

Architecture

The Kepler architecture is the successor to the Fermi architecture that first appeared in laptops with the GeForce 400M series. The GK104 Kepler core offers eight shader blocks, called SMX, that are clocked at the same speed as the central core. In the K4000M, 5 blocks are active leading to the 960 CUDA cores. Although more shader cores are available in the Kepler architecture as compared to the Fermi design, the Kepler shaders are still expected to be up to twice as power efficient. However, due to the missing hot clock of the shader domain, two shaders of a Kepler chip offer similar performance to just one shader of a Fermi chip (as the latter is clocked twice as fast). 

PCIe 3.0 is now supported by the mobile Kepler series and an optional Turbo mode can automatically overclock the Nvidia card by a theoretical 15 percent if the laptop cooling system allows it. The implementation of this boost mode is done in the BIOS, but it is ultimately dependent upon the manufacturer of the laptop.

Performance

The performance is significantly above the level of the older Quadro 5010M and also beats the GeForce GTX 675M. Therefore, the card will manage both CAD software and demanding 3D games of 2013 in high quality settings.

Features

The improved feature set now includes support for up to 4 active displays. Furthermore, high resolution monitors of up to 3840x2160 pixels can now be connected using DisplayPort 1.2 or HDMI 1.4a if available. HD-Audio codecs, such as Dolby TrueHD and DTS-HD, can be transmitted via bitstream mode through the HDMI port. However, as most laptops will feature Optimus, the integrated GPU will likely have direct control over the display ports and may limit the feature set available by the Nvidia Kepler cards.

The 5th generation PureVideo HD video processor (VP5) is also integrated in the GK107 core and offers hardware decoding of HD videos. Common codecs such as MPEG-1/2, MPEG-4 ASP, H.264 and VC1/WMV9 are fully supported up to 4K resolutions while VC1 and MPEG-4 are supported up to 1080p. Two streams can be decoded in parallel for features such as Picture-in-Picture. Another novelty is the inclusion of a dedicated video encoding engine similar to Intel QuickSync that can be accessed by the NVENC API.

The power consumption of the K4000M is rated at 100 Watt (TGP according to Nvidia) and is therefore suited for large-sized notebooks 17-inches or greater.

NVIDIA Quadro K510MNVIDIA Quadro K4000M
Quadro K Series
Quadro K5100M compare 1536 @ 0.77 GHz256 Bit @ 3600 MHz
Quadro K5000M compare 1344 @ 0.71 GHz256 Bit @ 3000 MHz
Quadro K4100M compare 1152 @ 0.71 GHz256 Bit @ 3200 MHz
Quadro K4000M 960 @ 0.6 GHz256 Bit @ 2800 MHz
Quadro K3100M compare 768 @ 0.71 GHz256 Bit @ 3200 MHz
Quadro K3000M compare 576 @ 0.65 GHz256 Bit @ 2800 MHz
Quadro K2100M compare 576 @ 0.67 GHz128 Bit @ 3000 MHz
Quadro K1100M compare 384 @ 0.71 GHz128 Bit @ 2800 MHz
Quadro K620M compare 384 @ 1.03 - 1.12 GHz64 Bit @ 2000 MHz
Quadro K2000M compare 384 @ 0.75 GHz128 Bit @ 1800 MHz
Quadro K1000M compare 192 @ 0.85 GHz128 Bit @ 1800 MHz
Quadro K610M compare 192 @ 0.95 GHz64 Bit @ 2600 MHz
Quadro K510M 192 @ 0.85 GHz64 Bit @ 2400 MHz
Quadro K500M compare 192 @ 0.85 GHz64 Bit @ 1800 MHz
Quadro K5100M compare 1536 @ 0.77 GHz256 Bit @ 3600 MHz
Quadro K5000M compare 1344 @ 0.71 GHz256 Bit @ 3000 MHz
Quadro K4100M compare 1152 @ 0.71 GHz256 Bit @ 3200 MHz
Quadro K4000M 960 @ 0.6 GHz256 Bit @ 2800 MHz
Quadro K3100M compare 768 @ 0.71 GHz256 Bit @ 3200 MHz
Quadro K3000M compare 576 @ 0.65 GHz256 Bit @ 2800 MHz
Quadro K2100M compare 576 @ 0.67 GHz128 Bit @ 3000 MHz
Quadro K1100M compare 384 @ 0.71 GHz128 Bit @ 2800 MHz
Quadro K620M compare 384 @ 1.03 - 1.12 GHz64 Bit @ 2000 MHz
Quadro K2000M compare 384 @ 0.75 GHz128 Bit @ 1800 MHz
Quadro K1000M compare 192 @ 0.85 GHz128 Bit @ 1800 MHz
Quadro K610M compare 192 @ 0.95 GHz64 Bit @ 2600 MHz
Quadro K510M 192 @ 0.85 GHz64 Bit @ 2400 MHz
Quadro K500M compare 192 @ 0.85 GHz64 Bit @ 1800 MHz
ArchitectureKeplerKepler
Pipelines192 - unified960 - unified
Core Speed846 MHz600 MHz
Memory Speed2400 MHz2800 MHz
Memory Bus Width64 Bit256 Bit
Memory TypeGDDR5GDDR5
Max. Amount of Memory1024 MB4 GB
Shared Memorynono
APIDirectX 11, Shader 5.0, OpenGL 4.3DirectX 11, Shader 5.0, OpenGL 4.1
Power Consumption30 Watt100 Watt
Transistors1.3 Billion
technology28 nm28 nm
FeaturesOptimus, PhysX, Verde Drivers, CUDA, OpenCL 1.2, 3DTV PlayOptimus, PhysX, Verde Drivers, CUDA, 3D Vision, 3DTV Play
Notebook Sizemedium sizedlarge
Date of Announcement23.07.2013 01.06.2012
Link to Manufacturer Pagehttp://www.nvidia.de/page/quadrofx_go.html
CodenameN14E-Q3

Benchmarks

Performance Rating - 3DMark 11 + Fire Strike + Time Spy - Quadro K4000M
10.4 pt (11%)
3DMark - 3DMark Cloud Gate Score
12751 Points (16%)
3DMark - 3DMark Cloud Gate Graphics
19058 Points (8%)
3DMark - 3DMark Fire Strike Standard Score
2192 Points (5%)
3DMark - 3DMark Fire Strike Standard Graphics
2199 Points (4%)
3DMark - 3DMark Ice Storm Graphics
150781 Points (20%)
3DMark 11 - 3DM11 Performance Score
min: 3673     avg: 3760     median: 3777 (8%)     max: 3830 Points
3DMark 11 - 3DM11 Performance GPU
min: 3413     avg: 3466     median: 3466 (5%)     max: 3519 Points
3DMark Vantage
3DM Vant. Perf. total + NVIDIA Quadro K4000M
3DMark Vantage - 3DM Vant. Perf. total
15362 Points (4%)
3DM Vant. Perf. GPU no PhysX + NVIDIA Quadro K4000M
3DMark Vantage - 3DM Vant. Perf. GPU no PhysX
min: 14010     avg: 14050     median: 14049.5 (11%)     max: 14089 Points
3DMark 06 3DMark 06 - Standard 1280x1024 + NVIDIA Quadro K4000M
3DMark 06
min: 19573     avg: 20223     median: 20518 (31%)     max: 20578 Points
Unigine Heaven 3.0 - Unigine Heaven 3.0 DX 11
36.5 fps (12%)
Unigine Heaven 2.1 - Heaven 2.1 high
48.5 fps (9%)
SPECviewperf 11
specvp11 snx-01 + NVIDIA Quadro K4000M
SPECviewperf 11 - specvp11 snx-01
34.7 fps (25%)
specvp11 tcvis-02 + NVIDIA Quadro K4000M
SPECviewperf 11 - specvp11 tcvis-02
40.3 fps (68%)
specvp11 sw-02 + NVIDIA Quadro K4000M
SPECviewperf 11 - specvp11 sw-02
39.7 fps (48%)
specvp11 proe-05 + NVIDIA Quadro K4000M
SPECviewperf 11 - specvp11 proe-05
12.2 fps (51%)
specvp11 maya-03 + NVIDIA Quadro K4000M
SPECviewperf 11 - specvp11 maya-03
51.3 fps (39%)
specvp11 lightwave-01 + NVIDIA Quadro K4000M
SPECviewperf 11 - specvp11 lightwave-01
42.8 fps (46%)
specvp11 ensight-04 + NVIDIA Quadro K4000M
SPECviewperf 11 - specvp11 ensight-04
40.5 fps (19%)
specvp11 catia-03 + NVIDIA Quadro K4000M
SPECviewperf 11 - specvp11 catia-03
45.6 fps (55%)
Windows 7 Experience Index - Win7 Gaming graphics
7.6 Points (96%)
Windows 7 Experience Index - Win7 Graphics
7.6 Points (96%)
Cinebench R10 Cinebench R10 Shading (32bit) + NVIDIA Quadro K4000M
Cinebench R10 - Cinebench R10 Shading (32bit)
6804 Points (29%)
Cinebench R11.5 Cinebench R11.5 OpenGL 64 Bit + NVIDIA Quadro K4000M
Cinebench R11.5 - Cinebench R11.5 OpenGL 64 Bit
70.9 fps (26%)
LuxMark v2.0 64Bit - LuxMark v2.0 Room GPU
101 Samples/s (0%)
LuxMark v2.0 64Bit - LuxMark v2.0 Sala GPU
221 Samples/s (0%)

Average Benchmarks NVIDIA Quadro K4000M → NAN% n=

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

low 1024x768
Quadro K4000M:
337  fps
med. 1366x768
Quadro K4000M:
129  fps
high 1366x768
Quadro K4000M:
98  fps
ultra 1920x1080
Quadro K4000M:
57  fps
low 1024x768
Quadro K4000M:
102  fps
med. 1366x768
Quadro K4000M:
73  fps
high 1366x768
Quadro K4000M:
62  fps
ultra 1920x1080
Quadro K4000M:
36  fps
Torchlight 2

Torchlight 2

2012
low 1024x768
Quadro K4000M:
98  fps
med. 1366x768
Quadro K4000M:
93  fps
ultra 1920x1080
Quadro K4000M:
86  fps
low 1024x768
Quadro K4000M:
89  fps
med. 1366x768
Quadro K4000M:
81  fps
high 1366x768
Quadro K4000M:
78  fps
ultra 1920x1080
Quadro K4000M:
34  fps
low 1024x768
Quadro K4000M:
247  fps
med. 1366x768
Quadro K4000M:
183  fps
high 1366x768
Quadro K4000M:
158  fps
ultra 1920x1080
Quadro K4000M:
83  fps
Anno 2070

Anno 2070

2011
low 1024x768
Quadro K4000M:
181  fps
med. 1366x768
Quadro K4000M:
90  fps
high 1366x768
Quadro K4000M:
54  fps
ultra 1920x1080
Quadro K4000M:
29  fps
low 1024x768
Quadro K4000M:
98  fps
med. 1366x768
Quadro K4000M:
72  fps
high 1366x768
Quadro K4000M:
51  fps
ultra 1920x1080
Quadro K4000M:
24  fps
Total War: Shogun 2

Total War: Shogun 2

2011
low 1024x768
Quadro K4000M:
228  fps
med. 1280x720
Quadro K4000M:
71  fps
ultra 1920x1080
Quadro K4000M:
24  fps
low 1024x768
Quadro K4000M:
248  fps
med. 1360x768
Quadro K4000M:
115  fps
high 1360x768
Quadro K4000M:
69  fps
ultra 1920x1080
Quadro K4000M:
48  fps
Anno 1404

Anno 1404

2009
low 1024x768
Quadro K4000M:
247  fps
ultra 1280x1024
Quadro K4000M:
92  fps
Half Life 2 - Lost Coast Benchmark

Half Life 2 - Lost Coast Benchmark

2005
high 1024x768
Quadro K4000M:
233  fps
World of Warcraft

World of Warcraft

2005
low 800x600
Quadro K4000M:
102  fps
med. 1024x768
Quadro K4000M:
105  fps
high 1280x1024
Quadro K4000M:
98  fps

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 08. 00:21:58

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

#1 checking url part for id 3241 +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, 03 Aug 2022 17:26:25 +0200 +0s ... 0s

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

#5 linkCache_getLink using $NBC_LINKCACHE +0.005s ... 0.053s

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

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

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

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

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

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

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

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

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

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

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

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

#18 composed specs +0s ... 0.054s

#19 did output specs +0s ... 0.054s

#20 start showIntegratedCPUs +0s ... 0.054s

#21 getting avg benchmarks for device 4835 +0.026s ... 0.08s

#22 got single benchmarks 4835 +0s ... 0.08s

#23 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.083s

#24 getting avg benchmarks for device 3241 +0.003s ... 0.085s

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

#26 got single benchmarks 3241 +0.007s ... 0.093s

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

#28 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.094s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#43 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.098s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#59 min, max, avg, median took s +0s ... 0.103s

#60 before gaming benchmark output +0s ... 0.103s

#61 Got 40 rows for game benchmarks. +0.006s ... 0.108s

#62 composed SQL query for gamebenchmarks +0s ... 0.108s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#84 got data and put it in $dataArray +0.001s ... 0.11s

#85 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.111s

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

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

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

#89 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.112s

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

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

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

#93 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.113s

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

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

#96 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 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 +0.001s ... 0.114s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#116 linkCache_getLink using $NBC_LINKCACHE +0s ... 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 +0.001s ... 0.118s

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

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

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

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

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

#125 benchmarks composed for output. +0s ... 0.12s

#126 calculated avg scores. +0s ... 0.12s

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

#128 return log +0.002s ... 0.123s

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)