Notebookcheck Logo

NVIDIA Quadro K510M vs NVIDIA Quadro K500M vs NVIDIA Quadro K3000M

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 K3000M

► remove from comparison NVIDIA Quadro K3000M

The NVIDIA Quadro K3000M is a performance-class, DirectX 11.1-compatible graphics card for mobile workstations. It is a Kepler-based GPU built on the GK104 chip (but using only 576 shader cores) and is manufactured in 28nm at TSMC. The Quadro K3000M is built for the Intel Chief River generation (Ivy Bridge) and is the successor to the Fermi-based Quadro 3000M (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 K3000M, 3 blocks are active leading to the 576 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 provide 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 slightly above the older Quadro 4000M based on the fermi architecture. Compared to consumer cards, the K3000M performs similar to the GeForce GT 750M. Games of 2013 can be played fluently in medium or high detail and resolution 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 K3000M is rated at 75 Watt (TGP according to Nvidia) and is therefore suited for medium-sized notebooks 17-inches or greater.

NVIDIA Quadro K510MNVIDIA Quadro K500MNVIDIA Quadro K3000M
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 - unified576 - unified
Core Speed846 MHz850 MHz654 MHz
Memory Speed2400 MHz1800 MHz2800 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 Watt75 Watt
Transistors1.3 Billion1.3 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, 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.html
CodenameN14M-Q1N14E-Q1
Information118mm2, CUDA, OpenCL 1.2, OpenGL 4.3

Benchmarks

3DMark 11 - 3DM11 Performance Score
min: 2645     avg: 2747     median: 2767 (6%)     max: 2809 Points
3DMark 11 - 3DM11 Performance GPU
min: 2383     avg: 2427     median: 2427 (3%)     max: 2471 Points
3DMark Vantage
3DM Vant. Perf. total + NVIDIA Quadro K3000M
3DMark Vantage - 3DM Vant. Perf. total
min: 11901     avg: 12106     median: 11902 (3%)     max: 12515 Points
3DM Vant. Perf. GPU no PhysX + NVIDIA Quadro K3000M
3DMark Vantage - 3DM Vant. Perf. GPU no PhysX
min: 9989     avg: 10067     median: 10037 (7%)     max: 10203 Points
3DMark 06 3DMark 06 - Standard 1280x1024 + NVIDIA Quadro K3000M
3DMark 06
min: 16863     avg: 17038     median: 17037.5 (25%)     max: 17212 Points
Unigine Heaven 2.1 - Heaven 2.1 high
min: 33.2     avg: 34.1     median: 34.1 (6%)     max: 35 fps
SPECviewperf 11
specvp11 snx-01 + NVIDIA Quadro K3000M
SPECviewperf 11 - specvp11 snx-01
min: 31.44     avg: 32.1     median: 31.5 (22%)     max: 33.2 fps
specvp11 tcvis-02 + NVIDIA Quadro K3000M
SPECviewperf 11 - specvp11 tcvis-02
min: 35.44     avg: 35.5     median: 35.5 (59%)     max: 35.7 fps
specvp11 sw-02 + NVIDIA Quadro K3000M
SPECviewperf 11 - specvp11 sw-02
min: 40.03     avg: 42.8     median: 42 (51%)     max: 46.4 fps
specvp11 proe-05 + NVIDIA Quadro K3000M
SPECviewperf 11 - specvp11 proe-05
min: 14.2     avg: 15.5     median: 15.3 (64%)     max: 17.02 fps
specvp11 maya-03 + NVIDIA Quadro K3000M
SPECviewperf 11 - specvp11 maya-03
min: 50.8     avg: 59.5     median: 51.6 (39%)     max: 76 fps
specvp11 lightwave-01 + NVIDIA Quadro K3000M
SPECviewperf 11 - specvp11 lightwave-01
min: 48.11     avg: 55.2     median: 50.4 (54%)     max: 67.1 fps
specvp11 ensight-04 + NVIDIA Quadro K3000M
SPECviewperf 11 - specvp11 ensight-04
min: 24.32     avg: 25.9     median: 24.3 (12%)     max: 29.1 fps
specvp11 catia-03 + NVIDIA Quadro K3000M
SPECviewperf 11 - specvp11 catia-03
min: 40.65     avg: 42     median: 41.7 (51%)     max: 43.6 fps
Windows 7 Experience Index - Win7 Gaming graphics
7.3 Points (92%)
Windows 7 Experience Index - Win7 Graphics
7.3 Points (92%)
Cinebench R10 Cinebench R10 Shading (32bit) + NVIDIA Quadro K3000M
Cinebench R10 - Cinebench R10 Shading (32bit)
min: 6804     avg: 6818     median: 6817.5 (5%)     max: 6831 Points
Cinebench R11.5 Cinebench R11.5 OpenGL 64 Bit + NVIDIA Quadro K3000M
Cinebench R11.5 - Cinebench R11.5 OpenGL 64 Bit
min: 57.9     avg: 59.4     median: 59.8 (22%)     max: 60.3 fps

Average Benchmarks NVIDIA Quadro K3000M → 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 K3000M:
71  fps
med. 1366x768
Quadro K3000M:
36  fps
high 1366x768
Quadro K3000M:
28  fps
ultra 1920x1080
Quadro K3000M:
11  fps
F1 2012

F1 2012

2012
low 1024x768
Quadro K3000M:
168  fps
med. 1366x768
Quadro K3000M:
141  fps
high 1366x768
Quadro K3000M:
125  fps
ultra 1920x1080
Quadro K3000M:
52  fps
Torchlight 2

Torchlight 2

2012
low 1024x768
Quadro K3000M:
128 132 ~ 130 fps
med. 1366x768
Quadro K3000M:
92 103 ~ 98 fps
ultra 1920x1080
Quadro K3000M:
87 95 ~ 91 fps
low 1024x768
Quadro K3000M:
96  fps
med. 1366x768
Quadro K3000M:
84  fps
high 1366x768
Quadro K3000M:
73  fps
ultra 1920x1080
Quadro K3000M:
23  fps
low 1024x768
Quadro K3000M:
172 185 ~ 179 fps
med. 1366x768
Quadro K3000M:
133 135 ~ 134 fps
high 1366x768
Quadro K3000M:
113 118 ~ 116 fps
ultra 1920x1080
Quadro K3000M:
72 73 ~ 73 fps
Anno 2070

Anno 2070

2011
low 1024x768
Quadro K3000M:
159  fps
med. 1366x768
Quadro K3000M:
62  fps
high 1366x768
Quadro K3000M:
39  fps
ultra 1920x1080
Quadro K3000M:
21  fps
low 1024x768
Quadro K3000M:
144  fps
med. 1366x768
Quadro K3000M:
124  fps
high 1366x768
Quadro K3000M:
80  fps
ultra 1920x1080
Quadro K3000M:
40  fps
low 1024x768
Quadro K3000M:
176  fps
high 1366x768
Quadro K3000M:
92  fps
ultra 1920x1080
Quadro K3000M:
34  fps
Total War: Shogun 2

Total War: Shogun 2

2011
low 1024x768
Quadro K3000M:
224 230 ~ 227 fps
med. 1280x720
Quadro K3000M:
54.5 55.1 ~ 55 fps
ultra 1920x1080
Quadro K3000M:
20.3 20.3 ~ 20 fps
low 1024x768
Quadro K3000M:
252  fps
med. 1360x768
Quadro K3000M:
75  fps
high 1360x768
Quadro K3000M:
59  fps
ultra 1920x1080
Quadro K3000M:
32  fps
low 800x600
Quadro K3000M:
98  fps
med. 1360x768
Quadro K3000M:
65  fps
high 1600x900
Quadro K3000M:
33  fps
ultra 1920x1080
Quadro K3000M:
10  fps
Anno 1404

Anno 1404

2009
low 1024x768
Quadro K3000M:
281  fps
ultra 1280x1024
Quadro K3000M:
63  fps
Sims 3

Sims 3

2009
low 800x600
Quadro K3000M:
341  fps
med. 1024x768
Quadro K3000M:
183  fps
high 1280x1024
Quadro K3000M:
130  fps
Half Life 2 - Lost Coast Benchmark

Half Life 2 - Lost Coast Benchmark

2005
high 1024x768
Quadro K3000M:
244  fps
World of Warcraft

World of Warcraft

2005
low 800x600
Quadro K3000M:
104 110 ~ 107 fps
med. 1024x768
Quadro K3000M:
158 159 ~ 159 fps
high 1280x1024
Quadro K3000M:
67 69 ~ 68 fps

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

v1.18
log 01. 01:30: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 3242 +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.066s ... 0.066s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#33 getting avg benchmarks for device 4835 +0.039s ... 0.11s

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

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

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

#37 getting avg benchmarks for device 3242 +0s ... 0.111s

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

#39 got single benchmarks 3242 +0.008s ... 0.12s

#40 got avg benchmarks for devices +0s ... 0.12s

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

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

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

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

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

#46 linkCache_getLink no uid found +0s ... 0.121s

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

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

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

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

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

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

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

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

#55 linkCache_getLink no uid found +0s ... 0.122s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#70 linkCache_getLink no uid found +0s ... 0.124s

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

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

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

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

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

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

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

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

#79 linkCache_getLink no uid found +0s ... 0.125s

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

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

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

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

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

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

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

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

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

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

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

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

#92 min, max, avg, median took s +0s ... 0.128s

#93 before gaming benchmark output +0s ... 0.128s

#94 Got 63 rows for game benchmarks. +0.005s ... 0.134s

#95 composed SQL query for gamebenchmarks +0s ... 0.134s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#126 got data and put it in $dataArray +0.002s ... 0.137s

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

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

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

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

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

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

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

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

#135 linkCache_getLink no uid found +0.001s ... 0.14s

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

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

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

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

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

#141 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.141s

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

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

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

#145 linkCache_getLink no uid found +0.001s ... 0.142s

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

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

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

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

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

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

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

#153 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.143s

#154 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.143s

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

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

#157 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.144s

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

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

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

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

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

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

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

#165 linkCache_getLink no uid found +0s ... 0.145s

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

#167 linkCache_getLink no uid found +0s ... 0.145s

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

#169 linkCache_getLink no uid found +0s ... 0.145s

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

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

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

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

#174 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.147s

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

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

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

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

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

#180 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.148s

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

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

#183 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.149s

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

#185 linkCache_getLink no uid found +0s ... 0.15s

#186 linkCache_getLink no uid found +0s ... 0.15s

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

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

#189 linkCache_getLink no uid found +0s ... 0.15s

#190 benchmarks composed for output. +0s ... 0.15s

#191 calculated avg scores. +0s ... 0.15s

#192 return log +0.001s ... 0.151s

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)