Related Articles

Hardware

This time around, we used the following benchmarking setup:

• CPU: E6700 Intel Core 2 Duo at 2.66 GHZ 
• Motherboard:  Asus P5W DH Deluxe
• Memory: 2 gigabytes of OCZ PC2 9200 DDR2 RAM (2 * 1024MB @ 1066 MHz[5-5-5-18]) 
• Power Supply: OCZ 850W GXS
• Hard Drive: 250 GB Seagate Barracuda 7200.10 SATA, w/16 MB cache
• CPU Cooler: Noctua NH-U 12
• OS: Vista-32,SP1

It seems odd that a $200 card is operating in the same league as the following assortment of heavy hitters used in our benchmarks, but it is the case. Those heavy hitters included a VisionTek HD3870X2 OC, a NVIDIA GTX 280, a Palit 9800GTX, and a Asus EN8800 GTS 512MB T.O.P. For comparison with some less expensive cards, we also included a Asus EN8800 GT T.O.P, a Gigabyte HD3870, and a Powercolor HD3850 Xtreme PCS.

Software

Driver-wise, I used NVIDIA's 175.16 Forceware drivers with everything but the GTX 280 which used Forceware 177.35's, while for the ATI cards, we used Catalyst 8.6 drivers, except for the HD4850, which used an unreleased driver supplied by ATI.

On the software side of things, here is the list of programs used:

Bioshock: For this benchmark, all of the Detail settings were set to 'High'. All of the graphic option switches were set to 'On', with the exception of the following three settings: Vsync, Windowed mode, and Force Global Lighting. We used FRAPS to measure frame rate performance. The FRAPS run was 138 seconds, triggered from pulling the switch in the sub at game's beginning. The sub's dive involves many big models moving around, which should strain the GPU's and be a good measure of the game's engine.

Call of Juarez: We used the stand-alone Call of Juarez DX10 benchmarking program for these results. For our AA testing, we used a setting of 2x.

Crysis: These benchmarks were performed using 'fly-by' GPU test found within the single-player pre-release demo version of the game. All graphic settings were on High.' For AA, we used a setting of 4x. DX10 mode was used. The game has also been fully patched (1.1).

Enemy Territory: Quake Wars: We use this id FPS benchmark to test out higher resolutions. We used the highest possible detail settings. We tested the resolutions at 4x AA as well as at 8x AA. 16x AF was also used.  

3DMark06 and 3DMark Vantage: These popular synthetic benchmarking programs were used at a resolution of 1280x1024. Vantage was run in 'Performance' mode, and only the two GPU tests were used.

Devil May Cry 4: Recently released, Devil May Cry 4 has an excellent stand-alone benchmarking program. Every graphics option was set to the highest possible quality setting (besides AA, which we did not use.) 

Media Error demo: A runner-up winner in the scene.org best demo category for 2007, this demo made by Fairlight , CNCD & Orange. If you have no idea what a demoscene demo is, you might want to go here for an explication, and it is recommended you follow the link above to see for yourself. Media Error in particular presents a serious work out for a video card. Although to my knowledge, no one in the history of hardware reviewing has used a demoscene demo for benchmarking purposes before now, demos such as these are naturally well-suited to the task. This demo was run at a 1600x1200 resolution, and FRAPS was used to measure framerate averages.   

If you would like any further information about our benchmark settings, feel free to ask us in the forums.