Notebookcheck Logo

NVIDIA Quadro K620M vs NVIDIA Quadro K510M vs NVIDIA Quadro K500M

NVIDIA Quadro K620M

► remove from comparison NVIDIA Quadro K620M

The Nvidia Quadro K620M is a DirectX 11 and OpenGL 4.5-compatible graphics card for mobile workstations. It is a Maxwell-based GPU built on the GM108 chip with 384 shader cores and manufactured in 28 nm by TSMC. The Quadro K620M is the successor to the significantly slower Quadro K610M. Usually, the GPU comes with 2 GB DDR3 memory clocked at 1000 MHz (2000 MHz effective, 16 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

Compared to Kepler, Maxwell has been optimized in several details to increase power efficiency. Smaller Streaming Multiprocessors (SMM) with only 128 ALUs (Kepler: 192) and an optimized scheduler should lead to better utilization of the shaders. Nvidia promises that a Maxwell SMM with 128 ALUs can offer 90% of the performance of a Kepler SMX with 192 ALUs. GM108 features 3 SMMs and thus 384 shader cores, 24 TMUs and 8 ROPs (64-bit interface).

Another optimization is the massively enlarged L2 cache. The larger size can reduce some of the memory traffic to allow for a relatively narrow memory interface without significantly hurting performance.

GM108 supports DirectX 11.2 (feature level 11.0 only) as well as DirectX 12.

Performance

Due to their identical specifications, the Quadro K620M offers a similar 3D gaming performance as the consumer GeForce 840M. Most games from 2014/2015 will run fluently in low or medium settings. Compared to other Quadro GPUs, the K620M performs almost similar to the older K1100M.

Features

The feature set should include support for up to 4 active displays. High-resolution monitors of up to 3840x2160 pixels can be connected using DisplayPort 1.2 or HDMI 1.4a (HDMI 2.0 not supported). 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, the cores of the Quadro K620M can be used for general calculations.

GM108 integrates the sixth generation of the PureVideo HD video engine (VP6), offering a better decoding performance for H.264 and MPEG-2 videos. Of course, VP6 supports all features of previous generations (4K support, PIP, video encoding via NVENC API).

Power Consumption

The power consumption of the Quadro K620M should be about 30 W including the board and memory components. Therefore, the GPU is best suited for laptops 13 - 14-inches in size and above. The K620M also supports Optimus to automatically switch between an integrated graphics card and the Nvidia GPU.

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 K620MNVIDIA Quadro K510MNVIDIA Quadro K500M
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
ArchitectureMaxwellKeplerKepler
Pipelines384 - unified192 - unified192 - unified
Core Speed1029 - 1124 (Boost) MHz846 MHz850 MHz
Memory Speed2000 MHz2400 MHz1800 MHz
Memory Bus Width64 Bit64 Bit64 Bit
Memory TypeDDR3GDDR5DDR3 / GDDR5
Max. Amount of Memory2048 MB1024 MB2048 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 Watt30 Watt35 Watt
technology28 nm28 nm28 nm
FeaturesOptimus, PhysX, CUDA, OpenCL, 3D Vision, 3DTV PlayOptimus, PhysX, Verde Drivers, CUDA, OpenCL 1.2, 3DTV PlayOptimus, PhysX, Verde Drivers, CUDA, 3D Vision, 3DTV Play
Date of Announcement01.03.2015 23.07.2013 01.06.2012
Link to Manufacturer Pagehttp://www.nvidia.de/object/mobile-works...http://www.nvidia.de/page/quadrofx_go.html
Transistors1.3 Billion1.3 Billion
Notebook Sizemedium sizedmedium sized
CodenameN14M-Q1
Information118mm2, CUDA, OpenCL 1.2, OpenGL 4.3

Benchmarks

Performance Rating - 3DMark 11 + Fire Strike + Time Spy - Quadro K620M
3.9 pt (4%)
3DMark - 3DMark Cloud Gate Score
6591 Points (7%)
3DMark - 3DMark Cloud Gate Graphics
9092 Points (4%)
3DMark - 3DMark Fire Strike Standard Score
1424 Points (3%)
3DMark - 3DMark Fire Strike Standard Graphics
1621 Points (3%)
3DMark - 3DMark Ice Storm Graphics
38601 Points (5%)
3DMark 11 - 3DM11 Performance Score
2526 Points (5%)
3DMark 11 - 3DM11 Performance GPU
2434 Points (3%)
3DMark Vantage
3DM Vant. Perf. total + NVIDIA Quadro K620M
3DMark Vantage - 3DM Vant. Perf. total
7880 Points (2%)
3DM Vant. Perf. GPU no PhysX + NVIDIA Quadro K620M
3DMark Vantage - 3DM Vant. Perf. GPU no PhysX
7268 Points (6%)
3DMark 06 3DMark 06 - Standard 1280x1024 + NVIDIA Quadro K620M
3DMark 06
10912 Points (16%)
Unigine Heaven 3.0 - Unigine Heaven 3.0 DX 11
21.9 fps (7%)
Unigine Heaven 3.0 - Unigine Heaven 3.0 OpenGL
18.6 fps (8%)
Unigine Heaven 2.1 - Heaven 2.1 high
29 fps (5%)
SPECviewperf 11
specvp11 snx-01 + NVIDIA Quadro K620M
SPECviewperf 11 - specvp11 snx-01
30.9 fps (22%)
specvp11 tcvis-02 + NVIDIA Quadro K620M
SPECviewperf 11 - specvp11 tcvis-02
39.5 fps (66%)
specvp11 sw-02 + NVIDIA Quadro K620M
SPECviewperf 11 - specvp11 sw-02
41.8 fps (51%)
specvp11 proe-05 + NVIDIA Quadro K620M
SPECviewperf 11 - specvp11 proe-05
15.7 fps (65%)
specvp11 maya-03 + NVIDIA Quadro K620M
SPECviewperf 11 - specvp11 maya-03
49.5 fps (37%)
specvp11 lightwave-01 + NVIDIA Quadro K620M
SPECviewperf 11 - specvp11 lightwave-01
46.8 fps (50%)
specvp11 ensight-04 + NVIDIA Quadro K620M
SPECviewperf 11 - specvp11 ensight-04
20.7 fps (10%)
specvp11 catia-03 + NVIDIA Quadro K620M
SPECviewperf 11 - specvp11 catia-03
46.7 fps (57%)
SPECviewperf 12
specvp12 sw-03 + NVIDIA Quadro K620M
SPECviewperf 12 - specvp12 sw-03
33 fps (14%)
specvp12 snx-02 + NVIDIA Quadro K620M
SPECviewperf 12 - specvp12 snx-02
17.1 fps (5%)
specvp12 showcase-01 + NVIDIA Quadro K620M
SPECviewperf 12 - specvp12 showcase-01
6.3 fps (2%)
specvp12 mediacal-01 + NVIDIA Quadro K620M
SPECviewperf 12 - specvp12 mediacal-01
7.1 fps (4%)
specvp12 maya-04 + NVIDIA Quadro K620M
SPECviewperf 12 - specvp12 maya-04
12 fps (4%)
specvp12 energy-01 + NVIDIA Quadro K620M
SPECviewperf 12 - specvp12 energy-01
0.4 fps (1%)
specvp12 creo-01 + NVIDIA Quadro K620M
SPECviewperf 12 - specvp12 creo-01
16.3 fps (9%)
specvp12 catia-04 + NVIDIA Quadro K620M
SPECviewperf 12 - specvp12 catia-04
18.7 fps (6%)
Windows 7 Experience Index - Win7 Gaming graphics
6.6 Points (84%)
Windows 7 Experience Index - Win7 Graphics
6.6 Points (84%)
Cinebench R10 Cinebench R10 Shading (32bit) + NVIDIA Quadro K620M
Cinebench R10 - Cinebench R10 Shading (32bit)
5261 Points (4%)
Cinebench R11.5 Cinebench R11.5 OpenGL 64 Bit + NVIDIA Quadro K620M
Cinebench R11.5 - Cinebench R11.5 OpenGL 64 Bit
49.2 fps (18%)
Cinebench R15
Cinebench R15 OpenGL 64 Bit + NVIDIA Quadro K620M
Cinebench R15 - Cinebench R15 OpenGL 64 Bit
60.6 fps (16%)
Cinebench R15 OpenGL Ref. Match 64 Bit + NVIDIA Quadro K620M
Cinebench R15 - Cinebench R15 OpenGL Ref. Match 64 Bit
99.6 % (100%)
GFXBench 3.0 - GFXBench 3.0 Manhattan
48.8 fps (13%)
GFXBench 3.0 - GFXBench 3.0 Manhattan Offscreen
60.3 fps (5%)
LuxMark v2.0 64Bit - LuxMark v2.0 Room GPU
253 Samples/s (1%)
LuxMark v2.0 64Bit - LuxMark v2.0 Sala GPU
508 Samples/s (1%)
ComputeMark v2.1 - ComputeMark v2.1 Result
1737 Points (3%)

Average Benchmarks NVIDIA Quadro K620M → 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
100%
Quadro K620M:
35  fps
med. 1366x768
100%
Quadro K620M:
23  fps
high 1920x1080
100%
Quadro K620M:
10  fps
low 1024x768
100%
Quadro K620M:
151  fps
med. 1366x768
100%
Quadro K620M:
76  fps
high 1920x1080
100%
Quadro K620M:
32  fps
ultra 1920x1080
100%
Quadro K620M:
18  fps
Thief

Thief

2014
low 1024x768
100%
Quadro K620M:
21  fps
med. 1366x768
100%
Quadro K620M:
26  fps
high 1366x768
100%
Quadro K620M:
13  fps
ultra 1920x1080
100%
Quadro K620M:
10  fps
low 1024x768
100%
Quadro K620M:
61  fps
med. 1366x768
100%
Quadro K620M:
48  fps
high 1366x768
100%
Quadro K620M:
40  fps
ultra 1920x1080
100%
Quadro K620M:
10.5  fps
low 1280x720
100%
Quadro K620M:
75  fps
med. 1366x768
100%
Quadro K620M:
59  fps
high 1366x768
100%
Quadro K620M:
22  fps
ultra 1920x1080
100%
Quadro K620M:
11  fps
low 1024x768
100%
Quadro K620M:
35  fps
med. 1366x768
100%
Quadro K620M:
31  fps
high 1366x768
100%
Quadro K620M:
21  fps
ultra 1920x1080
100%
Quadro K620M:
7  fps
GRID 2

GRID 2

2013
low 1024x768
100%
Quadro K620M:
128  fps
med. 1366x768
100%
Quadro K620M:
41  fps
high 1366x768
100%
Quadro K620M:
58  fps
ultra 1920x1080
100%
Quadro K620M:
20  fps
low 1024x768
100%
Quadro K620M:
49  fps
med. 1366x768
100%
Quadro K620M:
38  fps
high 1366x768
100%
Quadro K620M:
23  fps
ultra 1920x1080
100%
Quadro K620M:
11  fps
low 1280x720
100%
Quadro K620M:
73  fps
med. 1366x768
100%
Quadro K620M:
52  fps
high 1366x768
100%
Quadro K620M:
42  fps
ultra 1920x1080
100%
Quadro K620M:
15  fps
low 1024x768
100%
Quadro K620M:
134  fps
med. 1366x768
100%
Quadro K620M:
66  fps
high 1366x768
100%
Quadro K620M:
36  fps
med. 1366x768
100%
Quadro K620M:
23  fps
high 1366x768
100%
Quadro K620M:
22  fps
ultra 1920x1080
100%
Quadro K620M:
10  fps
low 1024x768
100%
Quadro K620M:
55  fps
med. 1366x768
100%
Quadro K620M:
37  fps
high 1366x768
100%
Quadro K620M:
26  fps
ultra 1920x1080
100%
Quadro K620M:
14  fps
low 1024x768
100%
Quadro K620M:
98  fps
med. 1366x768
100%
Quadro K620M:
62  fps
high 1366x768
100%
Quadro K620M:
38  fps
ultra 1920x1080
100%
Quadro K620M:
22  fps
F1 2012

F1 2012

2012
low 1024x768
100%
Quadro K620M:
111  fps
med. 1366x768
100%
Quadro K620M:
96  fps
high 1366x768
100%
Quadro K620M:
90  fps
ultra 1920x1080
100%
Quadro K620M:
47  fps
Torchlight 2

Torchlight 2

2012
low 1024x768
100%
Quadro K620M:
124  fps
med. 1366x768
100%
Quadro K620M:
105  fps
ultra 1920x1080
100%
Quadro K620M:
98  fps
low 1024x768
100%
Quadro K620M:
88  fps
med. 1366x768
100%
Quadro K620M:
44  fps
high 1366x768
100%
Quadro K620M:
31  fps
ultra 1920x1080
100%
Quadro K620M:
8  fps
low 1024x768
100%
Quadro K620M:
98  fps
med. 1366x768
100%
Quadro K620M:
75  fps
high 1366x768
100%
Quadro K620M:
52  fps
ultra 1920x1080
100%
Quadro K620M:
17  fps
low 1024x768
100%
Quadro K620M:
72  fps
med. 1366x768
100%
Quadro K620M:
57  fps
high 1366x768
100%
Quadro K620M:
59  fps
ultra 1920x1080
100%
Quadro K620M:
42  fps
Alan Wake

Alan Wake

2012
low 1024x768
100%
Quadro K620M:
41  fps
med. 1366x768
100%
Quadro K620M:
25  fps
ultra 1920x1080
100%
Quadro K620M:
13  fps
low 1024x768
100%
Quadro K620M:
101  fps
med. 1366x768
100%
Quadro K620M:
62  fps
high 1366x768
100%
Quadro K620M:
36  fps
ultra 1920x1080
100%
Quadro K620M:
16  fps
Total War: Shogun 2

Total War: Shogun 2

2011
low 1024x768
100%
Quadro K620M:
76  fps
med. 1280x720
100%
Quadro K620M:
36  fps
ultra 1920x1080
100%
Quadro K620M:
19  fps
low 1024x768
100%
Quadro K620M:
185  fps
med. 1360x768
100%
Quadro K620M:
79  fps
high 1360x768
100%
Quadro K620M:
54  fps
ultra 1920x1080
100%
Quadro K620M:
18  fps
World of Warcraft

World of Warcraft

2005
low 800x600
100%
Quadro K620M:
251  fps
med. 1024x768
100%
Quadro K620M:
152  fps
high 1280x1024
100%
Quadro K620M:
49  fps
ultra 1920x1080
100%
Quadro K620M:
26  fps

Average Gaming NVIDIA Quadro K620M → 100%

Average Gaming 30-70 fps → 100%

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

v1.18
log 27. 14:17:48

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

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

#2 checking url part for id 3239 +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 Thu, 22 Sep 2022 17:27:05 +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.067s

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

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

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

#17 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.069s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#33 getting avg benchmarks for device 6185 +0.046s ... 0.115s

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

#35 got single benchmarks 6185 +0.007s ... 0.123s

#36 getting avg benchmarks for device 4835 +0s ... 0.123s

#37 got single benchmarks 4835 +0s ... 0.123s

#38 getting avg benchmarks for device 3239 +0s ... 0.123s

#39 got single benchmarks 3239 +0s ... 0.123s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#80 min, max, avg, median took s +0s ... 0.138s

#81 before gaming benchmark output +0s ... 0.138s

#82 Got 86 rows for game benchmarks. +0.014s ... 0.152s

#83 composed SQL query for gamebenchmarks +0s ... 0.152s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#137 got data and put it in $dataArray +0.003s ... 0.156s

#138 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.157s

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

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

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

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

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

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

#145 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.158s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#165 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.162s

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

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

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

#169 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.163s

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

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

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

#173 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.163s

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

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

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

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

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

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

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

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

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

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

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

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

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

#187 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.166s

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

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

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

#191 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.167s

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

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

#194 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.168s

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

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

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

#198 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.169s

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

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

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

#202 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.17s

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

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

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

#206 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.17s

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

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

#209 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.171s

#210 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.171s

#211 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.171s

#212 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.171s

#213 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.172s

#214 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.172s

#215 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.172s

#216 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.173s

#217 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.173s

#218 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.173s

#219 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.173s

#220 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.174s

#221 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.174s

#222 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.174s

#223 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.174s

#224 benchmarks composed for output. +0s ... 0.174s

#225 calculated avg scores. +0s ... 0.174s

#226 return log +0.001s ... 0.175s

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)