Legit Video Card Reviews

NVIDIA GeForce GTX 580 SLI Benchmarking w/ ASUS ENGTX580

Manufacturer: ASUS
Product: ENGTX580/2DI/1536MD5
Date: Tue, Nov 30, 2010 - 12:00 AM
Written By: Nathan Kirsch -
Share:

FurMark 1.8.2

FurMark 1.8.2

FurMark is a very intensive OpenGL benchmark that uses fur rendering algorithms to measure the performance of the graphics card. Fur rendering is especially adapted to overheat the GPU and that's why FurMark is also a perfect stability and stress test tool (also called GPU burner) for the graphics card.

FurMark 1.8.2

The benchmark was rendered in full screen mode with no AA enabled on both video cards.

Furmark Benchmark Results

Benchmark Results: Furmark showed the NVIDIA GeForce GTX 580 performing poorly as the GTX580's new power monitoring hardware kicked on and slowed the card's performance down. NVIDIA said the GTX580 dynamically adjusts performance in certain applications (Furmark and OCCT) in order to keep the power within their specifications.  Here we see an example of where the new hardware monitoring management system hurts the card's performance. We have concerns about this, but NVIDIA said they can make changes in the driver, so if a game comes out down the road a simple driver update is all that is needed to change the power level. When running a pair of GeForce GTX 580 video cards in SLI we saw more than twice the performance of a single card.  This is also due to the power monitoring hardware on the video card as it is more relaxed in SLI as the algorithm used knows the cards will run hotter in an SLI system.

Next Page - Power Consumption


Review Index
Page 1 - ASUS GeForce GTX 580 Video Card
Page 2 - Retail Box and Bundle
Page 3 - The Test System
Page 4 - Aliens vs. Predator
Page 5 - Batman: Arkham Asylum GOTY
Page 6 - Just Cause 2
Page 7 - Metro 2033
Page 8 - S.T.A.L.K.E.R.: Call of Pripyat
Page 9 - H.A.W.X. 2 Benchmark
Page 10 - 3DMark Vantage
Page 11 - Unigine 'Heaven' DX11
Page 12 - FurMark 1.8.2
Page 13 - Power Consumption
Page 14 - ASUS GeForce GTX 580 Overclocking
Page 15 - Final Thoughts and Conclusion