MultiGPU Update: Two-GPU Options in Depth
by Derek Wilson on February 23, 2009 7:30 AM EST- Posted in
- GPUs
Power Consumption
All these results are taken at the wall (total system power) running the 3dmark Vantage POM (parallax occlusion mapping) shader test. This test uses very little other system resources and focuses on the GPU. This means that the numbers you see here are LOWER than total system power while playing a game -- often by more than 50W and sometimes 100W, depending on the game, benchmark and system. These numbers show clearer differences between GPU power draw, which is why we stick with them. These numbers should NOT be used to determine a proper PSU for a certain graphics card solution unless you consider a couple hundred watts of headroom in your calculation.
For idle power, NVIDIA's 55nm GT200 parts take the cake. We don't have a 55nm GTX 260 in house, but we would expect it's idle power to come in on par or lower than our GTX 285. AMD's 4850 hangs with the lower power NVIDIA options, but both the 512MB and 1GB 4870 variants pull more power than any of our other single GPU solutions.
For multiGPU options, SLI definitely draws the most power. The X2 single card multiGPU options are better than the two card solutions, and this carries over to NVIDIA as well with the GTX 295 coming in at lower power than 2x GTX 260s. If we had tested two 1GB 4870 cards, we would expect to see more than 285W power draw at idle, which is quite high indeed.
Things change up a bit when we explore load power draw. The lowest idle power parts end up drawing the most power under load. The additional draw of the GTX 280 and GTX 285 are not unexpected as they offer a typically higher level of performance for their power. All our multiGPU options do draw more power than all of our single GPU configurations, so, though we didn't calculate them, you can expect performance per watt advantages where ever a single GPU leads any multiGPU option in performance.
Facebook
Twitter
RSS
95 Comments
View All Comments
SiliconDoc - Wednesday, March 18, 2009 - link
Oh, I'm sorry go to that new technolo9gy red series the 3000 series, and get that 3780... that covers that GAP the reds have that they constantly WHINE nvidia has but DOES NOT.Yes, go back a full gpu gen for the reds card midrange...
GOOD GOLLY - how big have the reddies been lying? !?
HUGE!
MagicPants - Monday, February 23, 2009 - link
I know you're trying to isolate and rate only the video cards but the fact of the matter is if you spend $200 on a video card that bottlenecks a $3000 system you have made a poor choice. By your metrics integrated video would "win" a number of tests because it is more or less free.You should add a chart where you include the cost of the system. Also feel free to use something besides i7 965. Spending $1000 on a CPU in an article about CPU thrift seems wrong.
oldscotch - Monday, February 23, 2009 - link
I'm not sure that the article was trying to demonstrate how these cards compare in a $3000.00 system, as much as it was trying to eliminate any possibility of a CPU bottleneck.MagicPants - Monday, February 23, 2009 - link
Sure if the article was about pure performance this would make sense, but in performance per dollar it's out of place.If you build a system for $3000 and stick a $200 gtx 260 in it and get 30 fps you've just paid $106 ($3200/30fps)per fps.
Take that same $3000 dollar system and stick a $500 gtx 295 and assume you get 50 fps in the same game. Now you've paid just $70($3500/50fps) per fps.
In the context of that $3000 system the gtx 295 is the better buy because the system is "bottlenecking" the price.
OSJF - Monday, February 23, 2009 - link
What about micro stuttering in MultiGPU configurations?I just bought a HD4870 1GB today, the only reason i didn't choose a MultiGPU configuration was all the talkings about micro stuttering on german tech websites.
DerekWilson - Monday, February 23, 2009 - link
In general, we don't see micro stuttering except at high resolutions on memory intensive games that show average framerates that are already lowish ... games, hardware and drivers have gotten a bit better on that front when it comes to two GPUs to the point where we don't notice it as a problem when we do our hands on testing with two GPUs.chizow - Monday, February 23, 2009 - link
Nice job on the review Derek, certainly a big step up from recent reviews of the last 4-5 months. A few comments though:1) Would be nice to see what happens and start a step-back, CPU scaling with 1 GPU, 2 GPU and 3 CPU. Obviously you'd have to cut down the number of GPUs tested, but perhaps 1 from each generation as a good starting point for this analysis.
2) Some games where there's clearly artificial frame caps or limits, why wouldn't you remove them in your testing first? For example, Fallout 3 allows you to remove the frame cap/smoothing limit, which would certainly be more useful info than a bunch of SLI configs hitting 60FPS cap.
3) COD5 is interesting though, did you contact Treyarch about the apparent 60FPS limit for single-GPU solutions? I don't recall any such cap with COD4.
4) Is the 4850X2 still dependent on custom drivers from Sapphire? I've read some horror stories about official releases not being compatible with the 4850X2, which would certainly put owners behind the 8-ball as a custom driver would certainly have the highest risk of being dropped when it comes to support.
5) Would've been nice to have seen an overclocked i7 used, since its clearly obvious CPU bottlenecks are going to come into play even more once you go to 3 and 4 GPU solutions, while reducing the gain and scaling for the faster individual solutions.
Lastly, do you plan on discussing or investigating the impact of multi-threaded optimizations from drivers in Vista/Win7? You mentioned it in your DX11 article, but both Nvidia and ATI have already made improvements in their drivers, which seem to be directly credited for some of the recent driver gains. Particularly, I'd like to see if its a WDDM 1.0-1.1 benefit from multi-threaded driver that extends to DX9,10,11 paths, or if its limited strictly to WDDM 1.0-1.1 and DX10+ paths.
Thanks, look forward to the rest.
SiliconDoc - Wednesday, March 18, 2009 - link
Thank you very much." 2) Some games where there's clearly artificial frame caps or limits, why wouldn't you remove them in your testing first? For example, Fallout 3 allows you to remove the frame cap/smoothing limit, which would certainly be more useful info than a bunch of SLI configs hitting 60FPS cap.
3) COD5 is interesting though, did you contact Treyarch about the apparent 60FPS limit for single-GPU solutions? I don't recall any such cap with COD4.
4) Is the 4850X2 still dependent on custom drivers from Sapphire? I've read some horror stories about official releases not being compatible with the 4850X2, which would certainly put owners behind the 8-ball as a custom driver would certainly have the highest risk of being dropped when it comes to support.
"
#2 - a red rooster booster that limits nvidia winning by a large margin- unfairly.
#3 - Ditto
#4 - Ditto de opposite = this one boosts the red card unfairly
Yes, when I said "red fan boy" is all over Derek's articles, I meant it.
DerekWilson - Monday, February 23, 2009 - link
thanks for the feedback ... we'll consider some of this going forward.we did what we could to remove artificial frame caps. in fallout 3 we set ipresentinterval to 0 in both .ini files and framerate does go above 60 -- it just doesn't average above 60 so it looks like a vsync issue when it's an LOD issue.
we didn't contact anyone about COD5, though there's a console variable that's supposed to help but didn't (except for the multiGPU soluitons).
we're looking at doing overclocking tests as a follow up. not 100% on that, but we do see the value.
as for the Sapphire 4850 X2, part of the reason we didn't review it initially was because we couldn't get drivers. Ever since 8.12 we've had full driver support for the X2 from AMD. We didn't use any specialized drivers for that card at all.
we can look at the impact of multithreaded optimizations, but this will likely not come until DX11 as most of the stuff we talked about requires DX11 to work. I'll talk to NVIDIA and AMD about current multithreaded optimizations, and if they say there is anything useful to see in current drivers we'll check it out.
thanks again for the feedback
chizow - Monday, February 23, 2009 - link
Oh and specifically, much better layout/graph display with the resolution selections! :)