Notebookcheck Logo

NVIDIA Quadro K510M vs NVIDIA Quadro K500M vs NVIDIA Quadro K610M

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 K610M

► remove from comparison NVIDIA Quadro K610M

The NVIDIA Quadro K610M is a DirectX 11 and OpenGL 4.3 compatible graphics card for 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 K610M 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 K610M usually comes with 1 GB GDDR5 VRAM clocked at 650 MHz (2600 MHz effective, 20.8 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 K610M, 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 is clearly above the old Quadro K500M (which has only DDR3 memory) and similar to the consumer GeForce GT 720M. However, 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 K610M does not supprt 3D Vision Pro.

Using CUDA or OpenCL 1.2, the cores of the Quadro K610M 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 K610M 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 K510MNVIDIA Quadro K500MNVIDIA Quadro K610M
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 - unified192 - unified
Core Speed846 MHz850 MHz954 MHz
Memory Speed2400 MHz1800 MHz2600 MHz
Memory Bus Width64 Bit64 Bit64 Bit
Memory TypeGDDR5DDR3 / GDDR5GDDR5
Max. Amount of Memory1024 MB2048 MB1024 MB
Shared Memorynonono
APIDirectX 11, Shader 5.0, OpenGL 4.3DirectX 11, Shader 5.0, OpenGL 4.3DirectX 11, Shader 5.0, OpenGL 4.3
Power Consumption30 Watt35 Watt30 Watt
Transistors1.3 Billion1.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, OpenCL 1.2, 3DTV Play
Notebook Sizemedium sizedmedium sizedmedium sized
Date of Announcement23.07.2013 01.06.2012 23.07.2013
Link to Manufacturer Pagehttp://www.nvidia.de/page/quadrofx_go.htmlhttp://www.nvidia.de/page/quadrofx_go.html
CodenameN14M-Q1
Information118mm2, CUDA, OpenCL 1.2, OpenGL 4.3

Benchmarks

Performance Rating - 3DMark 11 + Fire Strike + Time Spy - Quadro K610M
3.2 pt (4%)
3DMark - 3DMark Cloud Gate Score
min: 5970     avg: 6052     median: 6051.5 (7%)     max: 6133 Points
3DMark - 3DMark Cloud Gate Graphics
min: 5836     avg: 5838     median: 5837.5 (2%)     max: 5839 Points
3DMark - 3DMark Fire Strike Standard Score
min: 711     avg: 713     median: 712.5 (2%)     max: 714 Points
3DMark - 3DMark Fire Strike Standard Graphics
min: 752     avg: 756     median: 755.5 (1%)     max: 759 Points
3DMark - 3DMark Ice Storm Graphics
min: 46346     avg: 46512     median: 46512 (6%)     max: 46678 Points
3DMark 11 - 3DM11 Performance Score
min: 1283     avg: 1295     median: 1294.5 (3%)     max: 1306 Points
3DMark 11 - 3DM11 Performance GPU
min: 1134     avg: 1144     median: 1143.5 (2%)     max: 1153 Points
3DMark Vantage
3DM Vant. Perf. total + NVIDIA Quadro K610M
3DMark Vantage - 3DM Vant. Perf. total
min: 4598     avg: 5116     median: 5116 (1%)     max: 5634 Points
3DM Vant. Perf. GPU no PhysX + NVIDIA Quadro K610M
3DMark Vantage - 3DM Vant. Perf. GPU no PhysX
min: 3572     avg: 3592     median: 3592 (2%)     max: 3612 Points
3DMark 06 3DMark 06 - Standard 1280x1024 + NVIDIA Quadro K610M
3DMark 06
8157 Points (12%)
Unigine Heaven 3.0 - Unigine Heaven 3.0 DX 11
9.4 fps (3%)
Unigine Heaven 3.0 - Unigine Heaven 3.0 OpenGL
9.2 fps (4%)
Unigine Heaven 2.1 - Heaven 2.1 high
13.8 fps (3%)
SPECviewperf 11
specvp11 snx-01 + NVIDIA Quadro K610M
SPECviewperf 11 - specvp11 snx-01
min: 20.54     avg: 20.9     median: 20.9 (15%)     max: 21.28 fps
specvp11 tcvis-02 + NVIDIA Quadro K610M
SPECviewperf 11 - specvp11 tcvis-02
min: 25.26     avg: 25.9     median: 25.9 (43%)     max: 26.47 fps
specvp11 sw-02 + NVIDIA Quadro K610M
SPECviewperf 11 - specvp11 sw-02
min: 35.16     avg: 35.6     median: 35.6 (43%)     max: 36.1 fps
specvp11 proe-05 + NVIDIA Quadro K610M
SPECviewperf 11 - specvp11 proe-05
min: 13.93     avg: 14.9     median: 14.9 (62%)     max: 15.9 fps
specvp11 maya-03 + NVIDIA Quadro K610M
SPECviewperf 11 - specvp11 maya-03
min: 35.14     avg: 38.8     median: 38.8 (29%)     max: 42.44 fps
specvp11 lightwave-01 + NVIDIA Quadro K610M
SPECviewperf 11 - specvp11 lightwave-01
min: 49.06     avg: 49.5     median: 49.5 (53%)     max: 49.84 fps
specvp11 ensight-04 + NVIDIA Quadro K610M
SPECviewperf 11 - specvp11 ensight-04
min: 14.67     avg: 15.9     median: 15.8 (8%)     max: 17.02 fps
specvp11 catia-03 + NVIDIA Quadro K610M
SPECviewperf 11 - specvp11 catia-03
min: 28.32     avg: 28.5     median: 28.5 (35%)     max: 28.72 fps
Windows 7 Experience Index - Win7 Gaming graphics
6.8 Points (86%)
Windows 7 Experience Index - Win7 Graphics
min: 5.7     avg: 6.3     median: 6.3 (79%)     max: 6.8 Points
Cinebench R10 Cinebench R10 Shading (32bit) + NVIDIA Quadro K610M
Cinebench R10 - Cinebench R10 Shading (32bit)
min: 6819     avg: 6824     median: 6823.5 (5%)     max: 6828 Points
Cinebench R11.5 Cinebench R11.5 OpenGL 64 Bit + NVIDIA Quadro K610M
Cinebench R11.5 - Cinebench R11.5 OpenGL 64 Bit
min: 27.95     avg: 28.4     median: 28.4 (10%)     max: 28.83 fps
LuxMark v2.0 64Bit - LuxMark v2.0 Room GPU
102 Samples/s (0%)
LuxMark v2.0 64Bit - LuxMark v2.0 Sala GPU
48 Samples/s (0%)

Average Benchmarks NVIDIA Quadro K610M → 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 1280x720
Quadro K610M:
44  fps
med. 1366x768
Quadro K610M:
32  fps
high 1366x768
Quadro K610M:
13  fps
ultra 1920x1080
Quadro K610M:
8  fps
GRID 2

GRID 2

2013
low 1024x768
Quadro K610M:
99.8  fps
med. 1366x768
Quadro K610M:
50.5  fps
high 1366x768
Quadro K610M:
35.7  fps
ultra 1920x1080
Quadro K610M:
12.5  fps
low 1024x768
Quadro K610M:
21.5  fps
med. 1366x768
Quadro K610M:
16.1  fps
high 1366x768
Quadro K610M:
9.1  fps
ultra 1920x1080
Quadro K610M:
4.8  fps
low 1280x720
Quadro K610M:
52.5  fps
med. 1366x768
Quadro K610M:
26.4  fps
high 1366x768
Quadro K610M:
22.2  fps
ultra 1920x1080
Quadro K610M:
6  fps
low 1024x768
Quadro K610M:
66.9  fps
med. 1366x768
Quadro K610M:
31.8  fps
high 1366x768
Quadro K610M:
20.7  fps
ultra 1920x1080
Quadro K610M:
4.9  fps
med. 1366x768
Quadro K610M:
33  fps
high 1366x768
Quadro K610M:
26  fps
ultra 1920x1080
Quadro K610M:
7  fps
low 1024x768
Quadro K610M:
38.8  fps
med. 1366x768
Quadro K610M:
23  fps
high 1366x768
Quadro K610M:
14.5  fps
ultra 1920x1080
Quadro K610M:
7.5  fps
low 1024x768
Quadro K610M:
119  fps
med. 1366x768
Quadro K610M:
31  fps
high 1366x768
Quadro K610M:
22  fps
ultra 1920x1080
Quadro K610M:
9  fps
F1 2012

F1 2012

2012
low 1024x768
Quadro K610M:
73  fps
med. 1366x768
Quadro K610M:
58  fps
high 1366x768
Quadro K610M:
52  fps
ultra 1920x1080
Quadro K610M:
21  fps
Torchlight 2

Torchlight 2

2012
low 1024x768
Quadro K610M:
48  fps
med. 1366x768
Quadro K610M:
109  fps
ultra 1920x1080
Quadro K610M:
47  fps
low 1024x768
Quadro K610M:
54.5  fps
med. 1366x768
Quadro K610M:
40.9  fps
high 1366x768
Quadro K610M:
14.8  fps
ultra 1920x1080
Quadro K610M:
5  fps
low 1024x768
Quadro K610M:
76  fps
med. 1366x768
Quadro K610M:
48  fps
high 1366x768
Quadro K610M:
32  fps
ultra 1920x1080
Quadro K610M:
9  fps
low 1024x768
Quadro K610M:
69  fps
med. 1366x768
Quadro K610M:
47  fps
high 1366x768
Quadro K610M:
43  fps
ultra 1920x1080
Quadro K610M:
25  fps
Alan Wake

Alan Wake

2012
low 1024x768
Quadro K610M:
26.8  fps
med. 1366x768
Quadro K610M:
16  fps
ultra 1920x1080
Quadro K610M:
6  fps
Anno 2070

Anno 2070

2011
low 1024x768
Quadro K610M:
62  fps
med. 1366x768
Quadro K610M:
31  fps
high 1366x768
Quadro K610M:
19  fps
ultra 1920x1080
Quadro K610M:
7  fps
low 1024x768
Quadro K610M:
72  fps
med. 1366x768
Quadro K610M:
48  fps
high 1366x768
Quadro K610M:
23  fps
ultra 1920x1080
Quadro K610M:
11  fps
Total War: Shogun 2

Total War: Shogun 2

2011
low 1024x768
Quadro K610M:
131.5  fps
med. 1280x720
Quadro K610M:
23.7  fps
ultra 1920x1080
Quadro K610M:
7.5  fps
World of Warcraft

World of Warcraft

2005
low 800x600
Quadro K610M:
345  fps
med. 1024x768
Quadro K610M:
132  fps
high 1280x1024
Quadro K610M:
27  fps
ultra 1920x1080
Quadro K610M:
12  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:08:45

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

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

#2 checking url part for id 4834 +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.051s ... 0.051s

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

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

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

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

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

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

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

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

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

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

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

#17 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.053s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#33 getting avg benchmarks for device 4835 +0.04s ... 0.094s

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

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

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

#37 getting avg benchmarks for device 4834 +0.005s ... 0.099s

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

#39 got single benchmarks 4834 +0.008s ... 0.107s

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

#41 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.108s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#87 min, max, avg, median took s +0s ... 0.119s

#88 before gaming benchmark output +0s ... 0.119s

#89 Got 68 rows for game benchmarks. +0.009s ... 0.128s

#90 composed SQL query for gamebenchmarks +0s ... 0.128s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#131 got data and put it in $dataArray +0.001s ... 0.131s

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

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

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

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

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

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

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

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

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

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

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

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

#144 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.134s

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

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

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

#148 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.134s

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

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

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

#152 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.135s

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

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

#155 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.135s

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

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

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

#159 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.137s

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

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

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

#163 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.137s

#164 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.137s

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

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

#167 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.139s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#185 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.142s

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

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

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

#189 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.142s

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

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

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

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

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

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

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

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

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

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

#200 benchmarks composed for output. +0s ... 0.144s

#201 calculated avg scores. +0s ... 0.144s

#202 return log +0.001s ... 0.145s

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)