Notebookcheck Logo

NVIDIA Quadro FX 570M vs NVIDIA Quadro FX 1700M

NVIDIA Quadro FX 570M

► remove from comparison

Performance Workstation Grafikchip mit DirectX 10 und OpenGL 2.1 Unterstützung der wahrscheinlich auf die NVIDIA GeForce 8600M GT basiert.

Gedacht für Digital Content Creators, Ingenieure, Geowissenschaftler und andere professionelle 3D Anwendungen.

Die Treiber der Quadro FX Serie sind zertifiziert für CAD Anwendungen (z.B. AutoCad, Inventor, Solidstation, Solid Edge, ...) und DCC Anwendungen (z.B. Maya, 3DS Max, Lightwave 3D, ...) und bieten eine 12-Bit-Präzision für Subpixel, Vollbild-Antialiasing, Hardwarebeschleunigtes Antialiasing für Punkte und Linien und weitere für CAD und DCC optimierte Einstellungen.

NVIDIA Quadro FX 1700M

► remove from comparison NVIDIA Quadro FX 1700M

Professionelle Grafikkarte mit zertifizierten Treiber besonders für OpenGL geeignet. Technisch ähnlich wie die Quadro FX 1600M (8700M) basiert die FX 1700M auf den 96x0M Kern (G96), jedoch mit höheren Taktraten. Im Vergleich zur 1600M wird bereits Powermizer 8.0 unterstützt.

Gedacht für Digital Content Creators, Ingenieure, Geowissenschaftler und andere professionelle 3D Anwendungen.

Zertifizierte Treiber garantieren die fehlerfreie und schnellere (im Vergleich zu 8700M) Darstellung von professionellen Programmen (CAD, CCD, Visualisierungssoftware).

NVIDIA Quadro FX 570MNVIDIA Quadro FX 1700M
Quadro FX Serie
Quadro FX 3800M compare 128 @ 0.68 GHz256 Bit @ 1000 MHz
Quadro FX 3700M compare 128 @ 0.55 GHz256 Bit @ 800 MHz
Quadro FX 2800M compare 96 @ 0.6 GHz256 Bit @ 1000 MHz
Quadro FX 3600M compare 96 @ 0.5 GHz256 Bit @ 800 MHz
Quadro FX 1800M compare 72 @ 0.56 GHz128 Bit @ 1100 MHz
Quadro FX 2700M compare 48 @ 0.53 GHz256 Bit @ 800 MHz
Quadro FX 880M compare 48 @ 0.55 GHz128 Bit @ 790 MHz
Quadro FX 3500M compare 24/8 cores @ 0.58 GHz256 Bit @ 700 MHz
Quadro FX 2500M compare 24/8 cores @ 0.5 GHz256 Bit @ 600 MHz
Quadro FX 1700M 32 @ 0.63 GHz128 Bit @ 800 MHz
Quadro FX 1600M compare 32 @ 0.63 GHz128 Bit @ 800 MHz
Quadro FX 1500M compare 20/7 cores @ 0.38 GHz256 Bit @ 500 MHz
Quadro FX 770M compare 32 @ 0.5 GHz128 Bit @ 800 MHz
Quadro FX 570M 32 @ 0.48 GHz128 Bit @ 700 MHz
Quadro FX 380M compare 16 @ 0.63 GHz64 Bit @ 800 MHz
Quadro FX 370M compare 8 @ 0.58 GHz64 Bit @ 700 MHz
Quadro FX 360M compare 16 @ 0.4 GHz64 Bit @ 600 MHz
Quadro FX 350M compare 4/3 cores @ 0.45 GHz64 Bit @ 350 MHz
Quadro FX 3800M compare 128 @ 0.68 GHz256 Bit @ 1000 MHz
Quadro FX 3700M compare 128 @ 0.55 GHz256 Bit @ 800 MHz
Quadro FX 2800M compare 96 @ 0.6 GHz256 Bit @ 1000 MHz
Quadro FX 3600M compare 96 @ 0.5 GHz256 Bit @ 800 MHz
Quadro FX 1800M compare 72 @ 0.56 GHz128 Bit @ 1100 MHz
Quadro FX 2700M compare 48 @ 0.53 GHz256 Bit @ 800 MHz
Quadro FX 880M compare 48 @ 0.55 GHz128 Bit @ 790 MHz
Quadro FX 3500M compare 24/8 cores @ 0.58 GHz256 Bit @ 700 MHz
Quadro FX 2500M compare 24/8 cores @ 0.5 GHz256 Bit @ 600 MHz
Quadro FX 1700M 32 @ 0.63 GHz128 Bit @ 800 MHz
Quadro FX 1600M compare 32 @ 0.63 GHz128 Bit @ 800 MHz
Quadro FX 1500M compare 20/7 cores @ 0.38 GHz256 Bit @ 500 MHz
Quadro FX 770M compare 32 @ 0.5 GHz128 Bit @ 800 MHz
Quadro FX 570M 32 @ 0.48 GHz128 Bit @ 700 MHz
Quadro FX 380M compare 16 @ 0.63 GHz64 Bit @ 800 MHz
Quadro FX 370M compare 8 @ 0.58 GHz64 Bit @ 700 MHz
Quadro FX 360M compare 16 @ 0.4 GHz64 Bit @ 600 MHz
Quadro FX 350M compare 4/3 cores @ 0.45 GHz64 Bit @ 350 MHz
CodenameG64GLMNB9P-GLM
ArchitekturG8xG9x
Pipelines32 - unified32 - unified
Kerntakt475 MHz625 MHz
Shadertakt950 MHz1250 MHz
Speichertakt700 MHz800 MHz
Speicherbandbreite128 Bit128 Bit
SpeichertypGDDR3GDDR3
Max. Speichergröße256 MB256 MB
Shared Memoryneinnein
APIDirectX 10, Shader 4.0DirectX 10, Shader 4.0
Stromverbrauch35 Watt50 Watt
Transistors289 Million289 Million
Herstellungsprozess80 nm65 nm
Notebookgrößemittel (15.4" z.B.)groß (17" z.B.)
Erscheinungsdatum01.06.2007 01.10.2008
InformationenPowermizer 7.0, CG Shading Hochsprache, 32 Bit Gleitkommapräzision, 12 Bit Subpixel Präzision, 128 Bit Genauigkeit der Grafikpipeline, Vertex und Pixelshader Programmierbarkeit, PureVideo HD, PCI-E Interface, FSAA mit gedrehtem Raster, nView Multidisplay Support, High-Precision Dynamic-Range (HPDR) Technologie, Hardware 3D Clipping nach Fensterkennung, Vollbild AntialiasingCG Shading Hochsprache, 32 Bit Gleitkommapräzision, 12 Bit Subpixel Präzision, 128 Bit Genauigkeit der Grafikpipeline, Vertex und Pixelshader Programmierbarkeit, PCI-E Interface, FSAA mit gedrehtem Raster, nView Multidisplay Support, High-Precision Dynamic-Range (HPDR) Technologie, Hardware 3D Clipping nach Fensterkennung, Vollbild Antialiasing
Herstellerseitehttp://www.nvidia.de/page/quadrofx_go.htmlhttp://www.nvidia.com/object/product_qua...
FeaturesOpenGL 2.1, PureVideo HD, Powermizer 8.0, mögliche Schnittstellen: LVDS, DVI, VGA, HDTV, HDCP, HDMI

Benchmarks

3DMark 2001SE - 3DMark 2001 - Standard
min: 24479     avg: 26908     median: 26907.5 (28%)     max: 29336 Points
35734 Points (37%)
3DMark 03 - 3DMark 03 - Standard
min: 11586     avg: 11958     median: 11957.5 (6%)     max: 12329 Points
18212 Points (10%)
3DMark 05 - 3DMark 05 - Standard
min: 7674     avg: 7790     median: 7700 (9%)     max: 7997 Points
11550 Points (13%)
3DMark 06 3DMark 06 - Score Unknown Settings + NVIDIA Quadro FX 570M
3DMark 06
3883 Points (6%)
3DMark 06 - Standard 1280x1024 + NVIDIA Quadro FX 570M
3DMark 06
3800 Points (6%)
3DMark 06 - Standard 1280x800 + NVIDIA Quadro FX 570M
3DMark 06
3904 Points (6%)
3DMark 06 - Standard 1280x800 + NVIDIA Quadro FX 1700M
6302 Points (9%)
Cinebench R10 Cinebench R10 Shading (32bit) + NVIDIA Quadro FX 570M
Cinebench R10 - Cinebench R10 Shading (32bit)
4534 Points (3%)
Cinebench R10 Shading (32bit) + NVIDIA Quadro FX 1700M
6159 Points (4%)
Cinebench R11.5 Cinebench R11.5 OpenGL 64 Bit + NVIDIA Quadro FX 570M
Cinebench R11.5 - Cinebench R11.5 OpenGL 64 Bit
9.3 fps (3%)

Average Benchmarks NVIDIA Quadro FX 570M → 100% n=5

Average Benchmarks NVIDIA Quadro FX 1700M → 146% n=5

- Bereich der Benchmarkergebnisse für diese Grafikkarte
- Durchschnittliche Benchmarkergebnisse für diese Grafikkarte
* Smaller numbers mean a higher performance
1 This benchmark is not used for the average calculation

Spiele-Benchmarks

Die folgenden Benchmarks basieren auf unseren Spieletests mit Testnotebooks. Die Performance dieser Grafikkarte bei den gelisteten Spielen ist abhängig von der verwendeten CPU, Speicherausstattung, Treiber und auch Betriebssystem. Dadurch müssen die untenstehenden Werte nicht repräsentativ sein. Detaillierte Informationen über das verwendete System sehen Sie nach einem Klick auf den fps-Wert.

Crysis - GPU Benchmark

Crysis - GPU Benchmark

2007
med. 1024x768
Quadro FX 1700M:
33.3  fps
high 1024x768
Quadro FX 1700M:
19.1  fps
Crysis - CPU Benchmark

Crysis - CPU Benchmark

2007
med. 1024x768
Quadro FX 1700M:
29.3  fps
high 1024x768
Quadro FX 1700M:
17.1  fps
F.E.A.R.

F.E.A.R.

2005
low 640x480
100%
Quadro FX 570M:
436  fps
87%
Quadro FX 1700M:
378  fps
med. 800x600
100%
Quadro FX 570M:
128  fps
119%
Quadro FX 1700M:
152  fps
high 1024x768
100%
Quadro FX 570M:
19 22 24 29 43 43 45 49 ~ 34 fps
174%
Quadro FX 1700M:
59  fps
Doom 3

Doom 3

2004
low 640x480
100%
Quadro FX 570M:
118  fps
med. 640x480
100%
Quadro FX 570M:
116.7  fps
high 800x600
100%
Quadro FX 570M:
111.3  fps
ultra 1024x768
100%
Quadro FX 570M:
89.7  fps
Quake 3 Arena - Timedemo

Quake 3 Arena - Timedemo

1999
high 1024x768
100%
Quadro FX 570M:
501  fps
122%
Quadro FX 1700M:
610  fps

Average Gaming NVIDIA Quadro FX 570M → 100%

Average Gaming 30-70 fps → 100%

Average Gaming NVIDIA Quadro FX 1700M → 125%

Average Gaming 30-70 fps → 174%

Eine Liste mit weiteren Spielen und allen Grafikkarten finden Sie auf unserer Seite: Welches Spiel ist mit welcher Grafikkarte spielbar?

Add one or more devices and compare

In the following list you can select (and also search for) devices that should be added to the comparison. You can select more than one device.

restrict list:

show all (including archived), 2022, 2021
v1.18
log 29. 01:15:22

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

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

#2 not redirecting to Ajax server +0s ... 0s

#3 did not recreate cache, as it is less than 5 days old! Created at Tue, 27 Sep 2022 17:27:11 +0200 +0.001s ... 0.001s

#4 linkCache_getLink using $NBC_LINKCACHE +0.105s ... 0.105s

#5 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.108s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#22 composed specs +0s ... 0.109s

#23 did output specs +0s ... 0.109s

#24 start showIntegratedCPUs +0s ... 0.109s

#25 getting avg benchmarks for device 182 +0.029s ... 0.138s

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

#27 got single benchmarks 182 +0.007s ... 0.146s

#28 getting avg benchmarks for device 1087 +0s ... 0.146s

#29 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.147s

#30 got single benchmarks 1087 +0.004s ... 0.151s

#31 got avg benchmarks for devices +0s ... 0.151s

#32 linkCache_getLink no uid found +0.001s ... 0.152s

#33 linkCache_getLink no uid found +0s ... 0.153s

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

#35 linkCache_getLink no uid found +0s ... 0.153s

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

#37 linkCache_getLink no uid found +0s ... 0.153s

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

#39 linkCache_getLink no uid found +0s ... 0.153s

#40 linkCache_getLink no uid found +0s ... 0.154s

#41 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.154s

#42 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.155s

#43 linkCache_getLink no uid found +0s ... 0.155s

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

#45 linkCache_getLink no uid found +0s ... 0.155s

#46 linkCache_getLink no uid found +0s ... 0.156s

#47 min, max, avg, median took s +0s ... 0.156s

#48 before gaming benchmark output +0s ... 0.156s

#49 Got 23 rows for game benchmarks. +0.003s ... 0.16s

#50 composed SQL query for gamebenchmarks +0s ... 0.16s

#51 got data and put it in $dataArray +0.001s ... 0.161s

#52 linkCache_getLink no uid found +0.001s ... 0.162s

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

#54 linkCache_getLink no uid found +0.001s ... 0.163s

#55 linkCache_getLink no uid found +0s ... 0.163s

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

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

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

#59 linkCache_getLink no uid found +0s ... 0.165s

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

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

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

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

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

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

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

#67 linkCache_getLink no uid found +0s ... 0.165s

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

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

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

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

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

#73 linkCache_getLink no uid found +0s ... 0.167s

#74 benchmarks composed for output. +0s ... 0.167s

#75 calculated avg scores. +0s ... 0.167s

#76 linkCache_getLink using $NBC_LINKCACHE +0.084s ... 0.251s

#77 return log +0.002s ... 0.254s

Teilen Sie diesen Artikel um uns zu unterstützen. Jeder Link hilft!
.170
> Notebook Test, Laptop Test und News > Benchmarks / Technik > Benchmarks / Technik > Grafikkarten Vergleich - Head 2 Head
Autor: Sebastian Jentsch,  8.09.2017 (Update: 19.05.2020)