NVIDIA Quadro P520 vs NVIDIA Quadro M1000M
Comparative analysis of NVIDIA Quadro P520 and NVIDIA Quadro M1000M videocards for all known characteristics in the following categories: Essentials, Technical info, Video outputs and ports, Compatibility, dimensions and requirements, API support, Memory, Technologies. Benchmark videocards performance analysis: PassMark - G2D Mark, PassMark - G3D Mark, Geekbench - OpenCL, GFXBench 4.0 - Car Chase Offscreen (Frames), GFXBench 4.0 - Car Chase Offscreen (Fps), GFXBench 4.0 - Manhattan (Frames), GFXBench 4.0 - Manhattan (Fps), GFXBench 4.0 - T-Rex (Frames), GFXBench 4.0 - T-Rex (Fps), CompuBench 1.5 Desktop - Face Detection (mPixels/s), CompuBench 1.5 Desktop - Ocean Surface Simulation (Frames/s), CompuBench 1.5 Desktop - T-Rex (Frames/s), CompuBench 1.5 Desktop - Video Composition (Frames/s), CompuBench 1.5 Desktop - Bitcoin Mining (mHash/s), 3DMark Fire Strike - Graphics Score.
Differences
Reasons to consider the NVIDIA Quadro P520
- Videocard is newer: launch date 3 year(s) 9 month(s) later
- Around 31% higher core clock speed: 1303 MHz vs 993 MHz
- Around 39% higher boost clock speed: 1493 MHz vs 1072 MHz
- 751.7x more texture fill rate: 23.89 GTexel/s vs 31.78 GTexel / s
- A newer manufacturing process allows for a more powerful, yet cooler running videocard: 14 nm vs 28 nm
- 1024x more maximum memory size: 2 GB vs 2 GB / 4 GB
- Around 20% higher memory clock speed: 6000 MHz vs 5012 MHz
Launch date | 27 May 2019 vs 18 August 2015 |
Core clock speed | 1303 MHz vs 993 MHz |
Boost clock speed | 1493 MHz vs 1072 MHz |
Texture fill rate | 23.89 GTexel/s vs 31.78 GTexel / s |
Manufacturing process technology | 14 nm vs 28 nm |
Maximum memory size | 2 GB vs 2 GB / 4 GB |
Memory clock speed | 6000 MHz vs 5012 MHz |
Reasons to consider the NVIDIA Quadro M1000M
- Around 33% higher pipelines: 512 vs 384
- 45x lower typical power consumption: 40 Watt vs 1800 million
- Around 30% better performance in PassMark - G2D Mark: 307 vs 237
- Around 36% better performance in PassMark - G3D Mark: 2835 vs 2091
- Around 11% better performance in Geekbench - OpenCL: 8849 vs 7960
- Around 19% better performance in GFXBench 4.0 - Car Chase Offscreen (Frames): 4196 vs 3527
- Around 19% better performance in GFXBench 4.0 - Car Chase Offscreen (Fps): 4196 vs 3527
- Around 4% better performance in GFXBench 4.0 - Manhattan (Frames): 3716 vs 3566
- Around 4% better performance in GFXBench 4.0 - Manhattan (Fps): 3716 vs 3566
- Around 46% better performance in GFXBench 4.0 - T-Rex (Frames): 3358 vs 2295
- Around 46% better performance in GFXBench 4.0 - T-Rex (Fps): 3358 vs 2295
Specifications (specs) | |
Pipelines | 512 vs 384 |
Thermal Design Power (TDP) | 40 Watt vs 1800 million |
Benchmarks | |
PassMark - G2D Mark | 307 vs 237 |
PassMark - G3D Mark | 2835 vs 2091 |
Geekbench - OpenCL | 8849 vs 7960 |
GFXBench 4.0 - Car Chase Offscreen (Frames) | 4196 vs 3527 |
GFXBench 4.0 - Car Chase Offscreen (Fps) | 4196 vs 3527 |
GFXBench 4.0 - Manhattan (Frames) | 3716 vs 3566 |
GFXBench 4.0 - Manhattan (Fps) | 3716 vs 3566 |
GFXBench 4.0 - T-Rex (Frames) | 3358 vs 2295 |
GFXBench 4.0 - T-Rex (Fps) | 3358 vs 2295 |
Compare benchmarks
GPU 1: NVIDIA Quadro P520
GPU 2: NVIDIA Quadro M1000M
PassMark - G2D Mark |
|
|
||||
PassMark - G3D Mark |
|
|
||||
Geekbench - OpenCL |
|
|
||||
GFXBench 4.0 - Car Chase Offscreen (Frames) |
|
|
||||
GFXBench 4.0 - Car Chase Offscreen (Fps) |
|
|
||||
GFXBench 4.0 - Manhattan (Frames) |
|
|
||||
GFXBench 4.0 - Manhattan (Fps) |
|
|
||||
GFXBench 4.0 - T-Rex (Frames) |
|
|
||||
GFXBench 4.0 - T-Rex (Fps) |
|
|
Name | NVIDIA Quadro P520 | NVIDIA Quadro M1000M |
---|---|---|
PassMark - G2D Mark | 237 | 307 |
PassMark - G3D Mark | 2091 | 2835 |
Geekbench - OpenCL | 7960 | 8849 |
GFXBench 4.0 - Car Chase Offscreen (Frames) | 3527 | 4196 |
GFXBench 4.0 - Car Chase Offscreen (Fps) | 3527 | 4196 |
GFXBench 4.0 - Manhattan (Frames) | 3566 | 3716 |
GFXBench 4.0 - Manhattan (Fps) | 3566 | 3716 |
GFXBench 4.0 - T-Rex (Frames) | 2295 | 3358 |
GFXBench 4.0 - T-Rex (Fps) | 2295 | 3358 |
CompuBench 1.5 Desktop - Face Detection (mPixels/s) | 38.33 | |
CompuBench 1.5 Desktop - Ocean Surface Simulation (Frames/s) | 721.18 | |
CompuBench 1.5 Desktop - T-Rex (Frames/s) | 3.056 | |
CompuBench 1.5 Desktop - Video Composition (Frames/s) | 42.938 | |
CompuBench 1.5 Desktop - Bitcoin Mining (mHash/s) | 137.786 | |
3DMark Fire Strike - Graphics Score | 1002 |
Compare specifications (specs)
NVIDIA Quadro P520 | NVIDIA Quadro M1000M | |
---|---|---|
Essentials |
||
Architecture | Pascal | Maxwell |
Code name | GP108 | GM107 |
Launch date | 27 May 2019 | 18 August 2015 |
Place in performance rating | 758 | 806 |
Type | Mobile workstation | Mobile workstation |
Launch price (MSRP) | $200.89 | |
Price now | $203.37 | |
Value for money (0-100) | 16.10 | |
Technical info |
||
Boost clock speed | 1493 MHz | 1072 MHz |
Core clock speed | 1303 MHz | 993 MHz |
Manufacturing process technology | 14 nm | 28 nm |
Peak Double Precision (FP64) Performance | 23.89 GFLOPS | |
Peak Half Precision (FP16) Performance | 11.94 GFLOPS | |
Peak Single Precision (FP32) Performance | 764.4 GFLOPS | |
Pipelines | 384 | 512 |
Pixel fill rate | 23.89 GPixel/s | |
Texture fill rate | 23.89 GTexel/s | 31.78 GTexel / s |
Thermal Design Power (TDP) | 1800 million | 40 Watt |
Floating-point performance | 1,017 gflops | |
Transistor count | 1,870 million | |
Video outputs and ports |
||
Display Connectors | No outputs | No outputs |
Multi monitor support | ||
Display Port | 1.2 | |
Compatibility, dimensions and requirements |
||
Height | PCIe 3.0 x16 | |
Laptop size | large | large |
Supplementary power connectors | None | None |
Interface | MXM-A (3.0) | |
API support |
||
DirectX | 12.1 | 12 |
OpenCL | 1.2 | |
OpenGL | 4.6 | 4.5 |
Shader Model | 6.4 | 5.0 |
Vulkan | ||
Memory |
||
Maximum RAM amount | 2 GB | 2 GB / 4 GB |
Memory bandwidth | 40.10 GB/s | 80 GB / s |
Memory bus width | 64 Bit | 128 Bit |
Memory clock speed | 6000 MHz | 5012 MHz |
Memory type | GDDR5 | GDDR5 |
Shared memory | 0 | |
Technologies |
||
Multi Monitor | ||
3D Vision Pro | ||
Mosaic | ||
nView Display Management | ||
Optimus |