NVIDIA Quadro M2000 vs NVIDIA Quadro P620

GPU Comparison Result

Below are the results of a comparison of NVIDIA Quadro M2000 and NVIDIA Quadro P620 video cards based on key performance characteristics, as well as power consumption and much more.

Advantages

  • Larger Memory Size: 4GB (4GB vs 2GB)
  • Higher Bandwidth: 105.8 GB/s (105.8 GB/s vs 80.13 GB/s)
  • More Shading Units: 768 (768 vs 512)
  • Higher Boost Clock: 1354MHz (1163MHz vs 1354MHz)
  • Newer Launch Date: February 2018 (April 2016 vs February 2018)

Basic

NVIDIA
Label Name
NVIDIA
April 2016
Launch Date
February 2018
Professional
Platform
Professional
Quadro M2000
Model Name
Quadro P620
Quadro
Generation
Quadro
796MHz
Base Clock
1266MHz
1163MHz
Boost Clock
1354MHz
PCIe 3.0 x16
Bus Interface
PCIe 3.0 x16
2,940 million
Transistors
3,300 million
48
TMUs
?
Texture Mapping Units (TMUs) serve as components of the GPU, which are capable of rotating, scaling, and distorting binary images, and then placing them as textures onto any plane of a given 3D model. This process is called texture mapping.
32
TSMC
Foundry
Samsung
28 nm
Process Size
14 nm
Maxwell 2.0
Architecture
Pascal

Memory Specifications

4GB
Memory Size
2GB
GDDR5
Memory Type
GDDR5
128bit
Memory Bus
?
The memory bus width refers to the number of bits of data that the video memory can transfer within a single clock cycle. The larger the bus width, the greater the amount of data that can be transmitted instantaneously, making it one of the crucial parameters of video memory. The memory bandwidth is calculated as: Memory Bandwidth = Memory Frequency x Memory Bus Width / 8. Therefore, when the memory frequencies are similar, the memory bus width will determine the size of the memory bandwidth.
128bit
1653MHz
Memory Clock
1252MHz
105.8 GB/s
Bandwidth
?
Memory bandwidth refers to the data transfer rate between the graphics chip and the video memory. It is measured in bytes per second, and the formula to calculate it is: memory bandwidth = working frequency × memory bus width / 8 bits.
80.13 GB/s

Theoretical Performance

37.22 GPixel/s
Pixel Rate
?
Pixel fill rate refers to the number of pixels a graphics processing unit (GPU) can render per second, measured in MPixels/s (million pixels per second) or GPixels/s (billion pixels per second). It is the most commonly used metric to evaluate the pixel processing performance of a graphics card.
21.66 GPixel/s
55.82 GTexel/s
Texture Rate
?
Texture fill rate refers to the number of texture map elements (texels) that a GPU can map to pixels in a single second.
43.33 GTexel/s
-
FP16 (half)
?
An important metric for measuring GPU performance is floating-point computing capability. Half-precision floating-point numbers (16-bit) are used for applications like machine learning, where lower precision is acceptable. Single-precision floating-point numbers (32-bit) are used for common multimedia and graphics processing tasks, while double-precision floating-point numbers (64-bit) are required for scientific computing that demands a wide numeric range and high accuracy.
21.66 GFLOPS
55.82 GFLOPS
FP64 (double)
?
An important metric for measuring GPU performance is floating-point computing capability. Double-precision floating-point numbers (64-bit) are required for scientific computing that demands a wide numeric range and high accuracy, while single-precision floating-point numbers (32-bit) are used for common multimedia and graphics processing tasks. Half-precision floating-point numbers (16-bit) are used for applications like machine learning, where lower precision is acceptable.
43.33 GFLOPS
1.822 TFLOPS
FP32 (float)
?
An important metric for measuring GPU performance is floating-point computing capability. Single-precision floating-point numbers (32-bit) are used for common multimedia and graphics processing tasks, while double-precision floating-point numbers (64-bit) are required for scientific computing that demands a wide numeric range and high accuracy. Half-precision floating-point numbers (16-bit) are used for applications like machine learning, where lower precision is acceptable.
1.358 TFLOPS

Miscellaneous

-
SM Count
?
Multiple Streaming Processors (SPs), along with other resources, form a Streaming Multiprocessor (SM), which is also referred to as a GPU's major core. These additional resources include components such as warp schedulers, registers, and shared memory. The SM can be considered the heart of the GPU, similar to a CPU core, with registers and shared memory being scarce resources within the SM.
4
768
Shading Units
?
The most fundamental processing unit is the Streaming Processor (SP), where specific instructions and tasks are executed. GPUs perform parallel computing, which means multiple SPs work simultaneously to process tasks.
512
48 KB (per SMM)
L1 Cache
48 KB (per SM)
1024KB
L2 Cache
1024KB
75W
TDP
40W
1.3
Vulkan Version
?
Vulkan is a cross-platform graphics and compute API by Khronos Group, offering high performance and low CPU overhead. It lets developers control the GPU directly, reduces rendering overhead, and supports multi-threading and multi-core processors.
1.3
3.0
OpenCL Version
3.0
4.6
OpenGL
4.6
12 (12_1)
DirectX
12 (12_1)
5.2
CUDA
6.1
None
Power Connectors
None
6.4
Shader Model
6.4
32
ROPs
?
The Raster Operations Pipeline (ROPs) is primarily responsible for handling lighting and reflection calculations in games, as well as managing effects like anti-aliasing (AA), high resolution, smoke, and fire. The more demanding the anti-aliasing and lighting effects in a game, the higher the performance requirements for the ROPs; otherwise, it may result in a sharp drop in frame rate.
16
250W
Suggested PSU
200W

Benchmarks

FP32 (float) / TFLOPS
Quadro M2000
1.822 +34%
Quadro P620
1.358
Blender
Quadro M2000
109
Quadro P620
128 +17%
OctaneBench
Quadro M2000
28 +17%
Quadro P620
24