Notebookcheck Logo

NVIDIA Quadro K510M vs NVIDIA Quadro K500M vs NVIDIA Quadro K5000M

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 K500M

► remove from comparison NVIDIA Quadro K500M

The NVIDIA Quadro K500M is an entry-level, DirectX 11.1-compatible graphics card for mobile workstations. It is a Kepler-based GPU built on the GK107 architecture and is manufactured in 28nm at TSMC. Compared to the K2000M, the K500M only features a 64-Bit memory bus and 192 shader cores instead of 384. The Quadro K500M is built for the Intel Chief River generation (Ivy Bridge) and is the successor to the Fermi-based Quadro 1000M (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 GK107 Kepler core offers two shader blocks, called SMX, each with 192 shaders for a total of 384 shader cores that are clocked at the same speed as the central core. The K500M, however, offers only one SMX with 192 shaders. 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 are about as fast as 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 gaming performance should be similar to the consumer GeForce GT 620M.

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 K500M is rated at 35 Watt (TGP according to Nvidia) and therefore suited for medium-sized notebooks of 15-inches or greater.

NVIDIA Quadro K5000M

► remove from comparison NVIDIA Quadro K5000M

The NVIDIA Quadro K5000M 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 1344 shader cores) and is manufactured in 28nm by TSMC. The Quadro K5000M is built for the Intel Chief River generation (Ivy Bridge) and is the successor to the Fermi-based Quadro 5010M (Huron River platform). Usually 4 GB GDDR5 graphics memory clocked at 750 MHz (3000 MHz effective) are used.

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 K5000M, 7 blocks are active leading to the 1366 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 clearly above the level of the older Quadro 5010M. Compared to the GTX 680M, the clock rates are sligthly lower (depending on the manufacturer), placing the card between the 680M and the Fermi based GTX 675M. Nevertheless, most demanding games of 2012 will run fluently with maxed out details.

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.

Using CUDA or OpenCL 1.2, the cores of the Quadro K5000M 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 K5000M is rated at 100 Watt (TGP according to Nvidia) and is therefore suited for large notebooks with 17-inch displays or greater.

NVIDIA Quadro K510MNVIDIA Quadro K500MNVIDIA Quadro K5000M
Quadro K Series
Quadro K5100M 1536 @ 0.77 GHz256 Bit @ 3600 MHz
Quadro K5000M 1344 @ 0.71 GHz256 Bit @ 3000 MHz
Quadro K4100M 1152 @ 0.71 GHz256 Bit @ 3200 MHz
Quadro K4000M 960 @ 0.6 GHz256 Bit @ 2800 MHz
Quadro K3100M 768 @ 0.71 GHz256 Bit @ 3200 MHz
Quadro K3000M 576 @ 0.65 GHz256 Bit @ 2800 MHz
Quadro K2100M 576 @ 0.67 GHz128 Bit @ 3000 MHz
Quadro K1100M 384 @ 0.71 GHz128 Bit @ 2800 MHz
Quadro K620M 384 @ 1.03 - 1.12 GHz64 Bit @ 2000 MHz
Quadro K2000M 384 @ 0.75 GHz128 Bit @ 1800 MHz
Quadro K1000M 192 @ 0.85 GHz128 Bit @ 1800 MHz
Quadro K610M 192 @ 0.95 GHz64 Bit @ 2600 MHz
Quadro K510M 192 @ 0.85 GHz64 Bit @ 2400 MHz
Quadro K500M 192 @ 0.85 GHz64 Bit @ 1800 MHz
Quadro K5100M 1536 @ 0.77 GHz256 Bit @ 3600 MHz
Quadro K5000M 1344 @ 0.71 GHz256 Bit @ 3000 MHz
Quadro K4100M 1152 @ 0.71 GHz256 Bit @ 3200 MHz
Quadro K4000M 960 @ 0.6 GHz256 Bit @ 2800 MHz
Quadro K3100M 768 @ 0.71 GHz256 Bit @ 3200 MHz
Quadro K3000M 576 @ 0.65 GHz256 Bit @ 2800 MHz
Quadro K2100M 576 @ 0.67 GHz128 Bit @ 3000 MHz
Quadro K1100M 384 @ 0.71 GHz128 Bit @ 2800 MHz
Quadro K620M 384 @ 1.03 - 1.12 GHz64 Bit @ 2000 MHz
Quadro K2000M 384 @ 0.75 GHz128 Bit @ 1800 MHz
Quadro K1000M 192 @ 0.85 GHz128 Bit @ 1800 MHz
Quadro K610M 192 @ 0.95 GHz64 Bit @ 2600 MHz
Quadro K510M 192 @ 0.85 GHz64 Bit @ 2400 MHz
Quadro K500M 192 @ 0.85 GHz64 Bit @ 1800 MHz
Quadro K5100M 1536 @ 0.77 GHz256 Bit @ 3600 MHz
Quadro K5000M 1344 @ 0.71 GHz256 Bit @ 3000 MHz
Quadro K4100M 1152 @ 0.71 GHz256 Bit @ 3200 MHz
Quadro K4000M 960 @ 0.6 GHz256 Bit @ 2800 MHz
Quadro K3100M 768 @ 0.71 GHz256 Bit @ 3200 MHz
Quadro K3000M 576 @ 0.65 GHz256 Bit @ 2800 MHz
Quadro K2100M 576 @ 0.67 GHz128 Bit @ 3000 MHz
Quadro K1100M 384 @ 0.71 GHz128 Bit @ 2800 MHz
Quadro K620M 384 @ 1.03 - 1.12 GHz64 Bit @ 2000 MHz
Quadro K2000M 384 @ 0.75 GHz128 Bit @ 1800 MHz
Quadro K1000M 192 @ 0.85 GHz128 Bit @ 1800 MHz
Quadro K610M 192 @ 0.95 GHz64 Bit @ 2600 MHz
Quadro K510M 192 @ 0.85 GHz64 Bit @ 2400 MHz
Quadro K500M 192 @ 0.85 GHz64 Bit @ 1800 MHz
ArchitectureKeplerKeplerKepler
Pipelines192 - unified192 - unified1344 - unified
Core Speed846 MHz850 MHz706 MHz
Memory Speed2400 MHz1800 MHz3000 MHz
Memory Bus Width64 Bit64 Bit256 Bit
Memory TypeGDDR5DDR3 / GDDR5GDDR5
Max. Amount of Memory1024 MB2048 MB4 GB
Shared Memorynonono
APIDirectX 11, Shader 5.0, OpenGL 4.3DirectX 11, Shader 5.0, OpenGL 4.3DirectX 11, Shader 5.0, OpenGL 4.1
Power Consumption30 Watt35 Watt100 Watt
Transistors1.3 Billion1.3 Billion3.5 Billion
technology28 nm28 nm28 nm
FeaturesOptimus, PhysX, Verde Drivers, CUDA, OpenCL 1.2, 3DTV PlayOptimus, PhysX, Verde Drivers, CUDA, 3D Vision, 3DTV PlayOptimus, PhysX, Verde Drivers, CUDA, OpenCL 1.2, 3D Vision, 3DTV Play
Notebook Sizemedium sizedmedium sizedlarge
Date of Announcement23.07.2013 01.06.2012 01.06.2012
Link to Manufacturer Pagehttp://www.nvidia.de/page/quadrofx_go.htmlhttp://www.nvidia.com/content/PDF/produc...
CodenameN14M-Q1N14E-Q5
Information118mm2, CUDA, OpenCL 1.2, OpenGL 4.3

Benchmarks

Performance Rating - 3DMark 11 + Fire Strike + Time Spy - Quadro K5000M
11.4 pt (13%)
3DMark - 3DMark Cloud Gate Score
min: 15362     avg: 16890     median: 16890 (18%)     max: 18418 Points
3DMark - 3DMark Cloud Gate Graphics
min: 22700     avg: 23061     median: 23060.5 (9%)     max: 23421 Points
3DMark - 3DMark Fire Strike Standard Score
min: 2724     avg: 2735     median: 2735 (7%)     max: 2746 Points
3DMark - 3DMark Fire Strike Standard Graphics
min: 2788     avg: 2798     median: 2797.5 (5%)     max: 2807 Points
3DMark - 3DMark Ice Storm Graphics
min: 124816     avg: 155947     median: 155946 (21%)     max: 187077 Points
3DMark 11 - 3DM11 Performance Score
min: 4328     avg: 4992     median: 5152 (10%)     max: 5180 Points
3DMark 11 - 3DM11 Performance GPU
min: 4879     avg: 4894     median: 4893 (7%)     max: 4910 Points
3DMark Vantage
3DM Vant. Perf. total + NVIDIA Quadro K5000M
3DMark Vantage - 3DM Vant. Perf. total
min: 19269     avg: 20341     median: 20139 (6%)     max: 22235 Points
3DM Vant. Perf. GPU no PhysX + NVIDIA Quadro K5000M
3DMark Vantage - 3DM Vant. Perf. GPU no PhysX
min: 17929     avg: 18096     median: 18089 (12%)     max: 18271 Points
3DMark 06 3DMark 06 - Standard 1280x1024 + NVIDIA Quadro K5000M
3DMark 06
min: 22348     avg: 23727     median: 24239 (35%)     max: 24595 Points
Unigine Heaven 3.0 - Unigine Heaven 3.0 DX 11
min: 47     avg: 47.5     median: 47.5 (16%)     max: 47.9 fps
Unigine Heaven 2.1 - Heaven 2.1 high
min: 62.7     avg: 63     median: 63 (12%)     max: 63.3 fps
SPECviewperf 11
specvp11 snx-01 + NVIDIA Quadro K5000M
SPECviewperf 11 - specvp11 snx-01
min: 38.25     avg: 53.6     median: 61.6 (44%)     max: 63.1 fps
specvp11 tcvis-02 + NVIDIA Quadro K5000M
SPECviewperf 11 - specvp11 tcvis-02
min: 40.79     avg: 52.7     median: 57.1 (96%)     max: 59.7 fps
specvp11 sw-02 + NVIDIA Quadro K5000M
SPECviewperf 11 - specvp11 sw-02
min: 37.1     avg: 49.8     median: 46.8 (57%)     max: 64.7 fps
specvp11 proe-05 + NVIDIA Quadro K5000M
SPECviewperf 11 - specvp11 proe-05
min: 10.82     avg: 14.7     median: 15.3 (64%)     max: 17.16 fps
specvp11 maya-03 + NVIDIA Quadro K5000M
SPECviewperf 11 - specvp11 maya-03
min: 56     avg: 86.5     median: 101 (76%)     max: 112.4 fps
specvp11 lightwave-01 + NVIDIA Quadro K5000M
SPECviewperf 11 - specvp11 lightwave-01
min: 44.87     avg: 59     median: 50.6 (54%)     max: 80.7 fps
specvp11 ensight-04 + NVIDIA Quadro K5000M
SPECviewperf 11 - specvp11 ensight-04
min: 47.12     avg: 53.1     median: 50.9 (24%)     max: 59.2 fps
specvp11 catia-03 + NVIDIA Quadro K5000M
SPECviewperf 11 - specvp11 catia-03
min: 38.78     avg: 54.5     median: 50.2 (61%)     max: 69.4 fps
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 K5000M
Cinebench R10 - Cinebench R10 Shading (32bit)
min: 6810     avg: 6814     median: 6814 (5%)     max: 6818 Points
Cinebench R11.5 Cinebench R11.5 OpenGL 64 Bit + NVIDIA Quadro K5000M
Cinebench R11.5 - Cinebench R11.5 OpenGL 64 Bit
min: 70.2     avg: 80.5     median: 83.5 (30%)     max: 88 fps
LuxMark v2.0 64Bit - LuxMark v2.0 Room GPU
min: 137     avg: 220.5     median: 220.5 (1%)     max: 304 Samples/s
LuxMark v2.0 64Bit - LuxMark v2.0 Sala GPU
min: 138     avg: 219.5     median: 219.5 (0%)     max: 301 Samples/s

Average Benchmarks NVIDIA Quadro K5000M → 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 K5000M:
222  fps
ultra 1920x1080
Quadro K5000M:
16.9  fps
low 1024x768
Quadro K5000M:
109 112 ~ 111 fps
med. 1366x768
Quadro K5000M:
78  fps
high 1366x768
Quadro K5000M:
71  fps
ultra 1920x1080
Quadro K5000M:
49 51 ~ 50 fps
F1 2012

F1 2012

2012
low 1024x768
Quadro K5000M:
155  fps
ultra 1920x1080
Quadro K5000M:
96  fps
low 1024x768
Quadro K5000M:
311 323 ~ 317 fps
med. 1366x768
Quadro K5000M:
232  fps
high 1366x768
Quadro K5000M:
209  fps
ultra 1920x1080
Quadro K5000M:
129 134 ~ 132 fps
Anno 2070

Anno 2070

2011
low 1024x768
Quadro K5000M:
252 279 ~ 266 fps
med. 1366x768
Quadro K5000M:
121  fps
high 1366x768
Quadro K5000M:
78  fps
ultra 1920x1080
Quadro K5000M:
39 40 ~ 40 fps
low 1024x768
Quadro K5000M:
82  fps
ultra 1920x1080
Quadro K5000M:
43  fps
Total War: Shogun 2

Total War: Shogun 2

2011
low 1024x768
Quadro K5000M:
261.4 267 ~ 264 fps
med. 1280x720
Quadro K5000M:
84.9 111 ~ 98 fps
ultra 1920x1080
Quadro K5000M:
37.9 40 ~ 39 fps
low 1024x768
Quadro K5000M:
271 302 ~ 287 fps
med. 1360x768
Quadro K5000M:
108  fps
high 1360x768
Quadro K5000M:
97  fps
ultra 1920x1080
Quadro K5000M:
55 58 ~ 57 fps
World of Warcraft

World of Warcraft

2005
low 800x600
Quadro K5000M:
102 402 ~ 252 fps
med. 1024x768
Quadro K5000M:
106 340 ~ 223 fps
high 1280x1024
Quadro K5000M:
103 121 ~ 112 fps

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

v1.18
log 30. 23:57:33

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

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

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

#5 linkCache_getLink using $NBC_LINKCACHE +0.093s ... 0.094s

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

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

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

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

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

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

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

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

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

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

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

#17 linkCache_getLink using $NBC_LINKCACHE +0.004s ... 0.098s

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

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

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

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

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

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

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

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

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

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

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

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

#30 composed specs +0s ... 0.098s

#31 did output specs +0s ... 0.098s

#32 start showIntegratedCPUs +0s ... 0.098s

#33 getting avg benchmarks for device 4835 +0.043s ... 0.141s

#34 got single benchmarks 4835 +0s ... 0.141s

#35 getting avg benchmarks for device 3239 +0s ... 0.141s

#36 got single benchmarks 3239 +0s ... 0.141s

#37 getting avg benchmarks for device 3240 +0.006s ... 0.147s

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

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

#40 got single benchmarks 3240 +0.01s ... 0.158s

#41 got avg benchmarks for devices +0s ... 0.158s

#42 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.159s

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

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

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

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

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

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

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

#50 linkCache_getLink no uid found +0.001s ... 0.161s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#83 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.165s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#102 linkCache_getLink no uid found +0s ... 0.167s

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

#104 linkCache_getLink no uid found +0s ... 0.167s

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

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

#107 linkCache_getLink no uid found +0s ... 0.167s

#108 linkCache_getLink no uid found +0s ... 0.168s

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

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

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

#112 linkCache_getLink no uid found +0s ... 0.168s

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

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

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

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

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

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

#119 linkCache_getLink no uid found +0s ... 0.169s

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

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

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

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

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

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

#126 min, max, avg, median took s +0s ... 0.171s

#127 before gaming benchmark output +0s ... 0.171s

#128 Got 42 rows for game benchmarks. +0.005s ... 0.175s

#129 composed SQL query for gamebenchmarks +0s ... 0.175s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#153 got data and put it in $dataArray +0s ... 0.176s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#176 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.18s

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

#178 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.181s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#196 benchmarks composed for output. +0s ... 0.182s

#197 calculated avg scores. +0s ... 0.182s

#198 return log +0.001s ... 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)