SLI vs. CrossFire, Part 1 – mid-range multi-GPU scaling & value
X3: Terran Conflict
X3:Terran Conflict (X3:TC) is another beautiful stand-alone benchmark that runs multiple tests and will really strain a lot of video cards. X3:TC is a space trading and combat simulator from Egosoft and is the most recent of their X-series of computer games. X3:TC is a standalone expansion of X3: Reunion, based in the same universe and on the same engine. It complements the story of previous games in the X-Universe and especially continues the events after the end of X3: Reunion. Compared to Reunion, Terran Conflict features a larger universe, more ships, and of course, new missions. The X-Universe is huge. The Terran faction was added with their own set of technology including powerful ships and stations. Many new weapons systems were developed for the expansion and it has generally received good reviews. It has a rather steep learning curve.
First we note the results at 2560×1600 with completely maxed out settings plus 8xAA:
Now we test at 1920×1200:
This time all of our video cards run close to each other in a fairly tight grouping except for the more budget cards. However, all of our video cards perform well and all of them experience similar minimum framerates and a similar playing experience. We also note no change in the minimums by adding a second card yet all of our cards in multi-GPU blow past the fastest video cards except for the very budget GTS 450 SLI setup.
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.