We all know for AMD company, they make one of the best graphic cards, processor in the world.Today i wanna to show you great article about AMD dual graphic, this combination give us impressive benchmarks result in video gaming or any work with graphic.Some people think that this benchmark result dont mean anything exactly and that gaming experience i almost same, let me know what do you think about this.
AMD Dual Graphics: Hybrid CrossFire, Reloaded
Update (8/16/2013): In light of your requests in the feedback section, we added Catalyst 13.8 beta video results to page nine of this review.
What AMD now calls Dual Graphics was originally referred to as Hybrid CrossFire. From a technical standpoint, the older designation was probably more on-point, since the feature leverages AMD’s multi-GPU technology as a means to scale the performance of an APU using discrete graphics.
Simply, that means you’re able to take an APU-powered system and add a Radeon card, link them together, and harness the resources of both to push frame rates higher than you’d see from either the APU or add-in card on its own.
The Dual Graphics brand was introduced alongside AMD’s Llano-based APUs in 2011, which I had the opportunity to review. While I acknowledged the appeal of Hybrid CrossFire, I experienced a few glitches with the original implementation. At the time, I hoped to revisit Dual Graphics once it matured. Over time, Llano gave way to Trinity, and Trinity was succeeded by Richland.
AMD had three generations to refine its hardware and software. So, we thought it high time to test Dual Graphics more thoroughly. After all, the company is making some pretty bold claims about the feature’s potential gains. The slide below comes from the press deck that accompanied Richland’s launch:
During the past two years, we’ve accumulated a handful of questions about Dual Graphics. For example, AMD recommends that you don’t imbalance its APUs with anything more than a Radeon HD 6670. And yet, we’ve heard that the Radeon HD 7750 makes a good accompaniment in a Dual Graphics array. Is it even possible to mix a VLIW5-based APU and a GCN-based add-in card using this technology? If so, do cards faster than the Radeon HD 6670 yield worthwhile results for the extra money you’re spending? Are there any Dual Graphics-related limitations you should know about? We’re setting out to answer those unknowns.
I also wanted to incorporate our FCAT-based analysis, which measures the dropped and runt (too small to perceive) frames generated by a multi-GPU configuration using video capture. Unfortunately, we can’t get the tool to successfully process video generated by Dual Graphics, and AMD tells us that the issue we’re encountering won’t be fixed in the foreseeable future. If you remember back to AMD A10-6700 And A10-6800K Review: Richland Hits The Desktop, the problem was that bits of adjacent frames would show up where there weren’t supposed to, like this:
See the tear in the image? We aren’t satisfied with this state of affairs, so we found another way to objectively evaluate the effectiveness of Dual Graphics: using the actual video capture we’d normally feed through FCAT to generate data. You’re going to be astonished by the dramatic results (at least, we certainly were). We’ll talk more about that video demonstration on the next page.
Video Demos, Test System And Benchmark Setup
We’ve always wanted to show you exactly what we see when we’re comparing the output of different graphics cards. The problem was that a lossless capture at 60 Hz and 1920×1080 yields a colossal video file that’s too large to download, really. On the other hand, putting the same file on YouTube cut its frame rate to 30 FPS, conveying half of the information from our original capture. Fortunately, we have a workaround thanks to YouTube’s HTML5 trial. Enable this beta feature by going to this page and clicking the “Join HTML5 Trial” button:
Once you’re in, close and relaunch your Web browser. You should now have access to HTML5-based speed controls through the settings button on the bottom-right of the video playback window:
We encoded our results at half-speed. So, at the YouTube “normal” speed setting (30 FPS), you can scrutinize the result at slower-than-real-time and get a great sense of the differences. Then, if you want to see the output as it appears when we’re testing, set the speed to 2x (60 FPS). Thanks to this technique, we have a powerful way to demonstrate the experience at 60 Hz, and you’re able to see what we do when we’re creating our benchmark results.
First, a few suggestions about the HTML5 trial. Make sure that the video loads completely before playing it back at 2x. This naturally requires more bandwidth, and you don’t want hiccups in the stream affecting your perception of the capture. Also, we’ve seen cases where YouTube doesn’t register a speed setting change until the page is reloaded. Finally, we recommend watching the video at normal speed before speeding it up. It’s much easier to see differences in frame rate smoothness this way.
You’ll notice that we’re using the Catalyst 13.6 Beta 2 driver instead of Catalyst 13.8 Beta, which adds a frame pacing feature for smoother, more consistent output. AMD tells us that the new driver does not affect Dual Graphics configurations. It only works with multiple discrete GPUs. Rest assured that the configuration we’re presenting is as up to date as possible.
||AMD A10-6800K (Richland) 4.1 GHz Base, 4.4 GHz Turbo Core w/ integrated Radeon HD 8670D (844 MHz)
||ASRock FM2A85X, Socket FM2, Chipset: AMD A85
||On-Board Gigabit LAN controller
||AMD Gamer Series Memory, 2 x 4 GB, 1866 MT/s, CL 13-13-13-34
||AMD Radeon HD 6670 DDR3
800 MHz GPU, 1 GB GDDR5 at 800 MHz (1600 MHz effective)
||Western Digital Caviar Black 750 GB
7200 RPM, 32 MB Cache, SATA 3Gb/s
||ePower EP-1200E10-T2 1200 W
|Software and Drivers
||Microsoft Windows 8 Pro x64
||AMD Catalyst 13.6 Beta 2
|Metro: Last Light
||Version 220.127.116.11, DirectX 10, Built-in Benchmark
|The Elder Scrolls V: Skyrim
||Version 1.6.89.06, Version 1.5.26.05, 25-Sec. Fraps
||Version 1.04, Custom THG Benchmark, 60-Sec. Fraps
||Version 1.2, Direct X 11, Built-in Benchmark, 60-Sec. Fraps
||Version 1.0.1441711, Built-in Benchmark, Fraps
|Company Of Heroes 2
||Version 18.104.22.16804, Built-in Benchmark, Fraps
Results: Tomb Raider
We begin our analysis with Tomb Raider, which is probably a best-case scenario for Dual Graphics since the title is sponsored by AMD. It also happens to be a lot of fun.
At least on paper, these benchmark results tell us that Dual Graphics has a pretty profound impact on performance, above and beyond what an APU on its own or an entry-level discrete GPU manages. As AMD suggests, its Radeon HD 6670 delivers the best price/performance ratio paired up to the A10-6800K APU, offering a 100% speed-up compared to the discrete card on its own.
The boost we measure from the GDDR5-equipped cards is less impressive. But despite mixing the VLIW5 and GCN architectures, there’s still a clear improvement.
Plotting frame rate over time doesn’t tell us anything different, though we see that the Dual Graphics setups deliver notably-higher frame rates than an APU or discrete GPU operating alone.
Now we take frame time variance into account. You can see that Dual Graphics introduces a significant amount of latency between subsequent frames. This latency can be responsible for dropped and runt frames, which counteract the benefit of a higher frame rate.
In the video below, you get a side-by-side comparison of the A10-6800K APU (24.1 FPS average), the A10-6800K APU with a Radeon HD 6670 DDR3 card in Dual Graphics mode (43.3 FPS average), and a Radeon HD 7750 on its own (49.2 FPS average).
The half-speed video gives us dramatic demonstration of what Fraps doesn’t tell us: the Dual Graphics configuration is as choppy as the A10-6800K on its own, despite a near-doubling of average frame rate. Meanwhile, the Radeon HD 7750 is perfectly smooth. This effect isn’t as severe at full-speed, but it’s still noticeable.
In this first title we’re testing, it’s quite obvious that there is a discrepancy between what you actually experience and what a benchmarking utility like Fraps suggests you should be seeing. The increase in frame time variance supports our hypothesis. Dual Graphics may increase the number of frames per second being rendered, but because they’re predominantly dropped and runt frames, you’re not actually seeing them during gameplay.
Results: The Elder Scrolls V: Skyrim
The Radeon HD 6670 cards provide a noticeable speed-up with Dual Graphics enabled, while the Radeon HD 7750 offers no benefit at all.
All of the test configurations are fairly consistent over the course of our benchmark.
Skyrim suffers from alarmingly high frame time variance in every single-GPU configuration except for the GCN-based Radeon HD 7750. Inexplicably, the variance actually decreases with Dual Graphics enabled, so we’re wondering if Dual Graphics does, in fact, improve the experience playing through this title.
Unfortunately, there is no correlation between frame time variance and perceived smoothness in Skyrim. The Radeon HD 6670 DDR3 in a Dual Graphics array averages 40.7 FPS, and that’s relatively close to the Radeon HD 7750′s 47.9 FPS average. But the actual experience is as choppy as an A10-6800K on its own, running at 23.8 FPS.
Results: Company Of Heroes 2
Even at its lowest detail settings, Company of Heroes 2 brutalizes our hardware at 1920×1080. A lower resolution would likely help, but these configurations simply don’t deliver a smooth experience as-tested. Technically, Dual Graphics does show a slight advantage over one card or APU on its own. But with minimum frame rates under 20, the results are hardly exciting.
Charting frame rate over time shows us that the low minimums we saw in the first chart aren’t symptomatic of a one-time dip. Performance actually falls under 30 FPS for a significant portion of the benchmark run.
The frame time variance in Company of Heroes 2 is extremely high. But the frame rates are so low that this probably isn’t important. Performance falls below what we consider playable, so there’s not much point in comparing the stutter-ridden output in video.
Results: F1 2012
AMD’s CrossFire technology for APUs and GPUs provides a small but measurable speed-up in this title. Only the Radeon HD 7750 gives us more than a 30 FPS minimum at these settings.
Dual Graphics appears to register more peaks and valleys than one GPU working alone when we plot frame rate over time.
In Dual Graphics mode, the Radeon HD 6670 cards exhibit a big increase in frame time variance. Let’s see how that translates to real-world gameplay:
Regardless of Fraps telling us that the average frame rate is higher, AMD’s Radeon HD 6670 DDR3 in Dual Graphics mode has just as many stuttering issues as the A10-6800K APU, if not more. Once again, the Radeon HD 7750 runs smoothly.
Results: Metro: Last Light
At the lowest detail settings, none of these graphics cards manage more than a 25 FPS minimum. Dual Graphics only improves the average frame rate when a DDR3-equipped Radeon HD 6670 is used; the boards with GDDR5 exhibit no benefit with the feature turned on.
Although the Radeon HD 7750 registers a minimum frame rate of 25 FPS, it rarely dips below 30 FPS. Thus, we consider the 7750 a suitable card for Metro: Last Light at these detail settings.
The Radeon HD 6670 complemented by DDR3 does poorly, as do the A10-6800K and 6670-based Dual Graphics configurations. Only the cards with GDDR5 memory demonstrate suitably low frame time variance.
Again, because Dual Graphics is not particularly playable, we’re skipping the video comparison.
Results: BioShock Infinite
Lastly, BioShock Infinite represents the latest developed with Epic’s Unreal Engine 3. Does Dual Graphics yield a frame rate boost in this AMD-sponsored title?
Indeed, it does. The Radeon HD 6670 DDR3 in Dual Graphics mode approaches Radeon HD 7750 performance, according to the averages measured by Fraps.
Charting out the frame rates over time reveals that only the Dual Graphics solutions and Radeon HD 7750 stay above 30 FPS for the vast majority of the benchmark.
The frame time variance definitely reflects additional latency with Dual Graphics enabled, but even the worst-case numbers aren’t terrible. We’ve seen gamers react to situations where variance was later measured at 5 ms, so this is in that realm. Of course, the video will tell us what we’re actually experiencing.
Despite the big difference in average frame rates, the A10-6800K (at 21.4 FPS) is almost indistinguishable from the Radeon HD 6670 DDR3 in Dual Graphics mode (at 37.3 FPS). The Radeon HD 7750 (at 42.6 FPS) is obviously far smoother than Dual Graphics, even though its average frame rate is only a little higher.
Update: Catalyst 13.8 Beta Driver Results
Update (8/16/2013): We received a lot of feedback asking for evidence that AMD’s Catalyst 13.8 beta driver does not improve the situation with Dual Graphics.
To be clear, a representative from the company previously stated that the Dual Graphics feature is not affected by this driver, including its frame pacing addition. Rather, 13.8 affects discrete cards in CrossFire.
With that said, we’re hear to help you make educated buying decisions. So, we spent the day capturing video using Catalyst 13.8 beta for your information.
As you can see, the new driver changes nothing as far as the Dual Graphics experience is concerned, just as AMD confirmed.
AMD Dual Graphics: Good For Benchmarks, Not For Gaming
Does adding a discrete graphics card to one of AMD’s APUs, enabling Dual Graphics, yield higher frame rates in your favorite games? Sure it does, according to Fraps.
But does it result in smoother gameplay, based on what you see rendered on-screen? After playing around with the feature ourselves, we didn’t think so. So, we went about looking for a way to demonstrate. Since FCAT doesn’t work due to issues with AMD’s driver, we stepped back and used the video we’d normally feed through FCAT instead. And the results aren’t pretty for Dual Graphics.
There’s a disconnect between the higher frame rates reported in Fraps and the what you actually see when you capture the DVI port’s output. This is a feature AMD has been talking about for almost two years now. Dual Graphics should be mature. We’re not sure how many mainstream gamers purchased a graphics card to go along with their Llano-, Trinity-, and Richland-based APUs, believing that they’d get a notably better experience, but from what we’re seeing, those additional investments are largely going to waste.
Yes, Fraps is telling us that the average frame rates are notably higher. However, this very conundrum was what inspired FCAT in the first place. If the software is counting every dropped and runt frame toward Dual Graphics’ average frame rate, then you’re getting absolutely no benefit from pieces of frames like the one pictured that are artificially inflating performance.
We’re not trying to pick on AMD. Despite knowledge of artifacts like micro-stuttering going back years, isolating experiential data is a more recent phenomenon championed by the team over at The Teach Report, and then further quantified through FCAT, developed by Nvidia. We’re very glad that AMD is taking these issues seriously enough that it developed a special driver to help address them. Indeed, we’ll be testing the latest Catalyst beta release shortly using the same technique, using it to see if the user experience improves with more consistent frame delivery. Assuming it does, we’ll happily dole out the praise to AMD’s software team.
With that said, the latest driver doesn’t help Dual Graphics. And the problems with this technology are more severe than we imagined even before this story was conceptualized. We’re hoping the company gets serious about fixing Dual Graphics, just as it did when it committed to improving CrossFire with two discrete GPUs. Right now it’s evangelizing a feature that helps improve benchmark results, but not actual gameplay. That’s just not right.