SLI vs. CrossFire, Part 1 – mid-range multi-GPU scaling & value
Metro 2033
Metro 2033 is the “Crysis” of 2010. It is a very demanding game on any PC with the very latest DX11 visuals. Metro 2033 is an action-oriented video game with a combination of survival horror, and first-person shooter elements. The game is based on the novel “Metro 2033” by Russian author Dmitry Glukhovsky. It was developed by 4A Games in Ukraine and released in March 2010. The game utilizes multi-platform 4A Engine and there is some doubt if the games engine is related to the original XRay engine used in S.T.A.L.K.E.R..
The Metro 2033 story takes place mostly in post-apocalyptic Moscow’s metro system but occasionally the player has to go above ground on some missions and to search for valuables. Metro 2033‘s locations reflect the dark atmosphere of real metro tunnels but in a much more dangerous and lethal manner. Strange phenomena and noises are frequent, and mostly the player has to rely only on their flashlight to find their way around in otherwise total darkness. Even more deadly is the surface as it is severely irradiated and a gas mask must be worn at all times due to the toxic air.
THQ has released an official benchmark for Metro 2033 which provides minimum/maximum/average framerates, and you can adjust many graphics settings including PhysX, AA, DOF and tessellation, and the number of runs. Our presets are set to maximum (very high) with 1xAA and no PhysX nor DOF enabled.
Here is our first chart at 1920×1200 as 2560×1600 proves too demanding without turning off most of the visuals that make this game really impressive. However, actually playing the game, one can tolerate minimums into the 20s without noticing severe lag.
We test at very High settings with AA and DOF off except as noted. Now at 1680×1050:
All of our single cards struggle with Metro 2033 with the aggressive settings that we used except for the GTX 580. Our GTX 570 is faster than the GTX 480 and they both lead the HD 5870. GTX 560 Ti sits between the HD 6950 and the HD 6870 while the HD 6850 and stock GTX 460s are far ahead of the GTS 450 which only matches a single HD 6870 in performance when it is paired with another in SLI.
Our HD 5870s in CrossFire trades blows with the GTX 560 Ti SLI performance; the CrossFired HD 6870 pair is not far behind, well ahead of GTX 460 SLI which trades blows with a single GTX 580.
I’m not 100% certain, but to analyze microstuttering, place a check in the box next to “Frametimes” in Fraps. Then when you press the hotkey, it will create a log file with a timestamp when each single frame was outputted. Only a few seconds is enough to make the log file really, really long. Then take a portion out of the log file and make a chart out of it, that measures the time between each timestamp, to see if the frames are consistent with each other in similar intervals, or if every other frame is too close to the other one.
If a game runs at say, 45fps with your SLI or CF setup, but feels more like 23-30fps, then definitely analyze this with FRAPS.
Great review so far.
How do the numbers change, if at all, if Split Frame Rendering is used instead of Alternate Frame Rendering?
The last time I used SLI was with my Voodoo2 3000s. It was a gigantic waste of $200, in 1996 dollars.
If SFR eliminates micro-stutter without too much of a performance penalty I might have to try SLI again.
why don’t they add BF:BC2?
and also 6950 n 6970 crossfire?
Concerning the microstutter, frames time (using that fraps option) is supposed to fluctuate more erratically on crossfire/sli than what it would be on a single card. I think instead of testing a moving scene, it would make more sense to test it on a completely still scene for a few seconds and see how they compare in the excel output file. You don’t want a moving scene because then you won’t be able to differentiate between the erracticness you would get from a moving scene and the erraticness you would get from microstutter.
Another interest option would be to downclock a sli/crossfire setup to a point where it matches the average framerate of the single card. This way you could could see if the multi-gpu setup looks choppier than a single card despite having the same average frame rate.
Excellent work! At the end, simple recommendations would have been nice. =)
Please include Civilization 5 if possible the next time you benchmark.
It is an important game which will test the tesselation feature and its scaling ability in multi-gpu configurations.
Civilization 5 has been added to my benching suite along with DiRT 3 and Total War, Shogun 2.
You’ve done a great job of benchmarking gaming performance, but including charts with FPS vs $$, and $$ vs wattage would be much more useful.
The wattage (both idle and load) figures can be especially important, as some of these cards can easily draw more juice than all but the most powerful (and expensive) power supplies can provide — and that definitely factors into the cost analysis.