Notebookcheck Logo

NVIDIA Quadro FX 1500M vs NVIDIA Quadro FX 380M vs NVIDIA Quadro FX 3500M

NVIDIA Quadro FX 1500M

► remove from comparison NVIDIA Quadro FX 1500M

NVIDIA Quadro FX 1500M is the version of 7900 GS video card for notebooks, which is optimized for CAD and professional 3D-applications. Technically, it has the same or similar chip (G71 architecture), but with other Bios and support for professional drivers.

The gaming performance is clearly worse than the 7900 GS (because of the application optimizing). Nonetheless, the most modded drivers can be used, so the Quadro FX 1500M is more a 7900 GS (for the operating system).

NVIDIA Quadro FX 380M

► remove from comparison NVIDIA Quadro FX 380M

The Nvidia Quadro FX 380M is a professional entry-level graphics card for mobile workstations. It is based on the GeForce 310M and therefore the 3D performance is not very good. Due to special drivers and optimizations, the performance for professional applications should be much better (than the 310M would perform). Another advantage are the certified drivers than ensure a good performance of professional applications without errors.

The card supports DirectX 10.1 and all the features of the G 310M (as it is based on the same GT218 core). Therefore PureVideo HD to decode HD videos with the graphics card is supported. The used Video Processor 4 (VP4) is able to fully decode H.264, VC-1, MPEG-2, and also MPEG-4 ASP (DivX or xVID) in hardware to minimize CPU load. MPEG-1 is not supported but can be easily handled by every modern CPU.

The gaming performance of the FX380M is similar to the GeForce 310M and therefore located in the entry level class. The professional drivers are however optimized for applications and may therefore deliver a worse performance. Modern 3D games like COD Modern Warfare 2 run only in low details and resolutions fluently. Some demanding games like NFS Shift or GTA4 wont run fluently at all. Less demanding games like SIMS 3 run in medium details and resolutions fluently. Therefore, the graphics card can not be recommended for gamers.

As the FX380M supports CUDA, DirectX Compute 10.1, and OpenCL, the shaders of the graphics processor can be used for other tasks than rendering images (e.g. faster encoding of videos).

The used GT218 core is manufactured in 40nm and based on the desktop GTX 200 architecture.

NVIDIA Quadro FX 3500M

► remove from comparison NVIDIA Quadro FX 3500M

The NVIDIA Quadro FX 3500M was the top professional graphic solution for the mobile use in 2007. The Quadro FX 3500M is especially suitable for CAD, digital image-, video editing and scientifical visualizations (according NVIDIA). It is based upon the NVIDIA GeForce Go 7950GTX. Therefore also a good gaming performance can be expected (for 2007 and if modded drivers are used). The card is shipped with certified drivers for professional applications, which are not optimized for games (inofficially the manual installation of Forceware drivers should be possible).

The drivers of the Quadro FX series are certified for CAD applications (e.g. AutoCad, Inventor, Solidstation, Solud Edge, ...) and DCC applictions (e.g. Maya, 3DS Max, Lightwave 3D, ...) and offers a 12-Bit precision for Subpixel, full image Antialiasing, hardware accelerated Antialiasing for dots and lines and additional optimized settings, which are optimized for CAD and DCC.

Nvidia describes the 3000 series as a power package for big laptops and data structures.

NVIDIA Quadro FX 1500MNVIDIA Quadro FX 380MNVIDIA Quadro FX 3500M
Quadro FX Series
Quadro FX 3800M 128 @ 0.68 GHz256 Bit @ 1000 MHz
Quadro FX 3700M 128 @ 0.55 GHz256 Bit @ 800 MHz
Quadro FX 2800M 96 @ 0.6 GHz256 Bit @ 1000 MHz
Quadro FX 3600M 96 @ 0.5 GHz256 Bit @ 800 MHz
Quadro FX 1800M 72 @ 0.56 GHz128 Bit @ 1100 MHz
Quadro FX 2700M 48 @ 0.53 GHz256 Bit @ 800 MHz
Quadro FX 880M 48 @ 0.55 GHz128 Bit @ 790 MHz
Quadro FX 3500M 24/8 cores @ 0.58 GHz256 Bit @ 700 MHz
Quadro FX 2500M 24/8 cores @ 0.5 GHz256 Bit @ 600 MHz
Quadro FX 1700M 32 @ 0.63 GHz128 Bit @ 800 MHz
Quadro FX 1600M 32 @ 0.63 GHz128 Bit @ 800 MHz
Quadro FX 1500M 20/7 cores @ 0.38 GHz256 Bit @ 500 MHz
Quadro FX 770M 32 @ 0.5 GHz128 Bit @ 800 MHz
Quadro FX 570M 32 @ 0.48 GHz128 Bit @ 700 MHz
Quadro FX 380M 16 @ 0.63 GHz64 Bit @ 800 MHz
Quadro FX 370M 8 @ 0.58 GHz64 Bit @ 700 MHz
Quadro FX 360M 16 @ 0.4 GHz64 Bit @ 600 MHz
Quadro FX 350M 4/3 cores @ 0.45 GHz64 Bit @ 350 MHz
Quadro FX 3800M 128 @ 0.68 GHz256 Bit @ 1000 MHz
Quadro FX 3700M 128 @ 0.55 GHz256 Bit @ 800 MHz
Quadro FX 2800M 96 @ 0.6 GHz256 Bit @ 1000 MHz
Quadro FX 3600M 96 @ 0.5 GHz256 Bit @ 800 MHz
Quadro FX 1800M 72 @ 0.56 GHz128 Bit @ 1100 MHz
Quadro FX 2700M 48 @ 0.53 GHz256 Bit @ 800 MHz
Quadro FX 880M 48 @ 0.55 GHz128 Bit @ 790 MHz
Quadro FX 3500M 24/8 cores @ 0.58 GHz256 Bit @ 700 MHz
Quadro FX 2500M 24/8 cores @ 0.5 GHz256 Bit @ 600 MHz
Quadro FX 1700M 32 @ 0.63 GHz128 Bit @ 800 MHz
Quadro FX 1600M 32 @ 0.63 GHz128 Bit @ 800 MHz
Quadro FX 1500M 20/7 cores @ 0.38 GHz256 Bit @ 500 MHz
Quadro FX 770M 32 @ 0.5 GHz128 Bit @ 800 MHz
Quadro FX 570M 32 @ 0.48 GHz128 Bit @ 700 MHz
Quadro FX 380M 16 @ 0.63 GHz64 Bit @ 800 MHz
Quadro FX 370M 8 @ 0.58 GHz64 Bit @ 700 MHz
Quadro FX 360M 16 @ 0.4 GHz64 Bit @ 600 MHz
Quadro FX 350M 4/3 cores @ 0.45 GHz64 Bit @ 350 MHz
Quadro FX 3800M 128 @ 0.68 GHz256 Bit @ 1000 MHz
Quadro FX 3700M 128 @ 0.55 GHz256 Bit @ 800 MHz
Quadro FX 2800M 96 @ 0.6 GHz256 Bit @ 1000 MHz
Quadro FX 3600M 96 @ 0.5 GHz256 Bit @ 800 MHz
Quadro FX 1800M 72 @ 0.56 GHz128 Bit @ 1100 MHz
Quadro FX 2700M 48 @ 0.53 GHz256 Bit @ 800 MHz
Quadro FX 880M 48 @ 0.55 GHz128 Bit @ 790 MHz
Quadro FX 3500M 24/8 cores @ 0.58 GHz256 Bit @ 700 MHz
Quadro FX 2500M 24/8 cores @ 0.5 GHz256 Bit @ 600 MHz
Quadro FX 1700M 32 @ 0.63 GHz128 Bit @ 800 MHz
Quadro FX 1600M 32 @ 0.63 GHz128 Bit @ 800 MHz
Quadro FX 1500M 20/7 cores @ 0.38 GHz256 Bit @ 500 MHz
Quadro FX 770M 32 @ 0.5 GHz128 Bit @ 800 MHz
Quadro FX 570M 32 @ 0.48 GHz128 Bit @ 700 MHz
Quadro FX 380M 16 @ 0.63 GHz64 Bit @ 800 MHz
Quadro FX 370M 8 @ 0.58 GHz64 Bit @ 700 MHz
Quadro FX 360M 16 @ 0.4 GHz64 Bit @ 600 MHz
Quadro FX 350M 4/3 cores @ 0.45 GHz64 Bit @ 350 MHz
CodenameG71GLMn10m-glmG71GLM
ArchitectureG7xGT2xxG7x
Pipelines20 / 7 Pixel- / Vertexshader16 - unified24 / 8 Pixel- / Vertexshader
Core Speed375 MHz625 MHz575 MHz
Memory Speed500 MHz800 MHz700 MHz
Memory Bus Width256 Bit64 Bit256 Bit
Memory TypeGDDR3GDDR3, DDR3GDDR3
Max. Amount of Memory512 MB512 MB512 MB
Shared Memorynonono
APIDirectX 9c, Shader 3.0DirectX 10.1, Shader 4.1DirectX 9c, Shader 3.0
Power Consumption20 Watt25 Watt45 Watt
Transistors278 Million260 Million278 Million
technology90 nm40 nm90 nm
Features90nmDirectX Compute Support (Windows 7), CUDA, OpenCL, OpenGL 2.1, certified drivers12-bit-sub-pixel, 32-bit-floating-point precision, 32-bit floating point precision, 128 bit graphic pipeline, hardware 3D window clipping, high precision dynamic-range (DPDR) technology, unified memory architecture, nView multi-display (for multi-monitor support), PowerMizer options for energy saving, architecture which is optimized for workstations, rotated-grid full-scene antialiasing (RG FSAA), unified driver architecture, NVIDIA PureVideo technology
Notebook Sizelargelarge
Date of Announcement18.04.2006 07.01.2010 01.03.2007
InformationPCI-E, 90nm
Link to Manufacturer Pagehttp://www.nvidia.de/page/quadrofx_go.htmlhttp://www.nvidia.com/object/product_qua...http://www.nvidia.com/page/quadrofx_go.h...
Shader Speed1530 MHz

Benchmarks

3DMark 2001SE - 3DMark 2001 - Standard
26279 Points (27%)
3DMark 03 - 3DMark 03 - Standard
min: 14650     avg: 15283     median: 15283 (8%)     max: 15916 Points
20736 Points (11%)
3DMark 05 - 3DMark 05 - Standard
min: 6386     avg: 6666     median: 6400 (9%)     max: 7212 Points
7095 Points (10%)
9295 Points (13%)
3DMark 06 3DMark 06 - Score Unknown Settings + NVIDIA Quadro FX 1500M
3DMark 06
min: 3900     avg: 3903     median: 3903 (6%)     max: 3906 Points
3DMark 06 - Score Unknown Settings + NVIDIA Quadro FX 380M
3690 Points (6%)
3DMark 06 - Score Unknown Settings + NVIDIA Quadro FX 3500M
5254 Points (8%)
3DMark 06 - Standard 1280x1024 + NVIDIA Quadro FX 1500M
3DMark 06
4074 Points (6%)
3DMark 06 - Standard 1280x1024 + NVIDIA Quadro FX 380M
3687 Points (6%)

Average Benchmarks NVIDIA Quadro FX 1500M → 100% n=2

Average Benchmarks NVIDIA Quadro FX 380M → 103% n=2

Average Benchmarks NVIDIA Quadro FX 3500M → 140% n=2

- 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.

F.E.A.R.

F.E.A.R.

2005
low 640x480
100%
Quadro FX 1500M:
259  fps
med. 800x600
100%
Quadro FX 1500M:
143  fps
high 1024x768
100%
Quadro FX 1500M:
63  fps
Doom 3

Doom 3

2004
low 640x480
100%
Quadro FX 1500M:
114.5  fps
med. 640x480
100%
Quadro FX 1500M:
113.6  fps
high 800x600
100%
Quadro FX 1500M:
113.9  fps
ultra 1024x768
100%
Quadro FX 1500M:
109.3  fps
Quake 3 Arena - Timedemo

Quake 3 Arena - Timedemo

1999
high 1024x768
100%
Quadro FX 1500M:
380.7  fps

Average Gaming NVIDIA Quadro FX 1500M → 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.17
log 01. 19:00:24

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

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

#2 checking url part for id 61 +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 Wed, 29 Jun 2022 17:25:55 +0200 +0s ... 0s

#5 linkCache_getLink using $NBC_LINKCACHE +0.047s ... 0.048s

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

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

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

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

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

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

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

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

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

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

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

#17 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

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

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

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

#21 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.05s

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

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

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

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

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

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

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

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

#30 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#31 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#32 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#33 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#34 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#35 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#36 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#37 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#38 composed specs +0s ... 0.05s

#39 did output specs +0s ... 0.05s

#40 start showIntegratedCPUs +0s ... 0.05s

#41 getting avg benchmarks for device 7 +0.041s ... 0.091s

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

#43 got single benchmarks 7 +0.006s ... 0.098s

#44 getting avg benchmarks for device 1620 +0s ... 0.098s

#45 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.099s

#46 got single benchmarks 1620 +0.004s ... 0.102s

#47 getting avg benchmarks for device 61 +0s ... 0.103s

#48 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.103s

#49 got single benchmarks 61 +0.003s ... 0.107s

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

#51 linkCache_getLink no uid found +0.001s ... 0.107s

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

#53 linkCache_getLink no uid found +0s ... 0.108s

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

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

#56 linkCache_getLink no uid found +0s ... 0.109s

#57 linkCache_getLink no uid found +0s ... 0.109s

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

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

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

#61 linkCache_getLink no uid found +0s ... 0.11s

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

#63 linkCache_getLink no uid found +0s ... 0.11s

#64 min, max, avg, median took s +0s ... 0.111s

#65 before gaming benchmark output +0s ... 0.111s

#66 Got 8 rows for game benchmarks. +0.002s ... 0.113s

#67 composed SQL query for gamebenchmarks +0s ... 0.113s

#68 got data and put it in $dataArray +0.001s ... 0.113s

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

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

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

#72 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 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 +0.001s ... 0.117s

#77 benchmarks composed for output. +0s ... 0.117s

#78 calculated avg scores. +0s ... 0.117s

#79 return log +0.001s ... 0.118s

Please share our article, every link counts!
> Notebook / Laptop Reviews and News > Benchmarks / Tech > Graphics Card Comparison - Head 2 Head
Redaktion, 2017-09- 8 (Update: 2017-09-11)