Page 2:Underground Stream: A GPGPU History
Page 3:Whither Avivo Video Converter?
Page 4:The “Balanced Platform”
Page 5:CyberLink Serves Up Espresso
Page 6:Let’s Pull Some Shots!
Page 7:Add Shots
Page 8:Mixed Messages
Page 9:Heavier Lifting
Page 10:Sim(ply Not Ready)HD
Page 11:In AMD’s Words
Page 12:Why Only These Codecs?
Page 13:Putting The “General” In GPGPU
Page 14:AMD On Stream’s Prospects
The “Balanced Platform”
Despite that the phrase “balanced platform” just aches of being something that emerged from a marketing round table, it’s worth pausing here to explain some good thinking on AMD’s part. If you harken back to our CUDA coverage, you’ll recall that one of our greatest praises for Badaboom was that it exhibited some of the lowest CPU usage from the field of competing CUDA encoders—“low” being utilization in the 60% instead of 95% range. Transcoding is incredibly compute-intensive, and the de facto reasoning among software vendors seems to be that users want their jobs done as quickly as possible. If that means sacking the CPU and GPU concurrently to the exclusion of practically all other tasks, so be it. We have yet to see a Stream or CUDA application with a resource utilization slider.
But that doesn’t mean hardware vendors have to take the same approach. AMD’s “balanced platform” concept tries to leverage several major components of the system and spread the load as evenly as possible, doing the same work in the same time but leaving enough overhead for other applications to still function normally. That sounds pretty, but how well does it pan out in real life?
I hit on an excellent example of the balanced platform at work in our very first Espresso test, which involved taking a YouTube HD video (MPEG-4, 1280x720) and transcoding it into the iPhone 640x360 profile, which is also H.264 MPEG-4. The two images below show performance with the HD 4890. On the left, you see the test run without GPU acceleration, and on the right you have Stream enabled. You can see that with CPU-only encoding, all four cores of our Phenom II are practically maxed and GPU-Z registers the GPU load at a fairly steady and minimal 6%, which probably represents some element of the UVD pipeline being exercised during transcoding. In the GPU-enabled capture, you see a typical pattern emerge. Core 2 stays hammered (we don’t know why so many encoder utilities lean on this particular core) but cores 1, 3, and 4 drop down to sub-50% levels while the GPU load jumps.
The obvious next question is whether Nvidia, without a so-called balanced platform at its back, delivers similar results under CUDA. The question is a bit tricky to answer given our test setup because GPU-Z fails to display the GPU Load readout with the Nvidia card installed. Still, we can infer some things by CPU results and final performance. You’ll note in the left shot that CPU-only utilization looks topped out—very similar to AMD. When we add CUDA into the mix (right image), CPU utilization remains almost unchanged.
So is CUDA doing anything? You bet. There’s a 35% drop in output time with GPU acceleration enabled, so CUDA is plainly throwing everything it can at the job. But here’s the interesting part: AMD and Nvidia show essentially the same encode time in CPU-only mode, but Stream yields a 108% performance gain, easily trouncing the CUDA result while averaging 40% less CPU utilization than CUDA.
As we’ll see, this is not a universal result. There are times when CUDA shines brighter. But tests like this show that AMD’s balanced platform statements are based on real benefits, not empty marketing meant to sell processors.
- Underground Stream: A GPGPU History
- Whither Avivo Video Converter?
- The “Balanced Platform”
- CyberLink Serves Up Espresso
- Let’s Pull Some Shots!
- Add Shots
- Mixed Messages
- Heavier Lifting
- Sim(ply Not Ready)HD
- In AMD’s Words
- Why Only These Codecs?
- Putting The “General” In GPGPU
- AMD On Stream’s Prospects