AMD FirePro V9800 4 GB: Eyefinity Meets Professional Graphics

Benchmark Results: Adobe CS5 Suite

Our standard Photoshop benchmark is optimized for threading, but it’s not built to test the few OpenGL-accelerated tasks Photoshop can execute. Thus, it’s hardly surprising to see both graphics cards turning back identical performance.

Our After Effects project doesn’t make extensive use of the Mercury Playback Engine. Nevertheless, Nvidia gets the job done just a little faster.

Our render job finishes faster on Nvidia’s Quadro 5000, but the Adobe Media Encoder task is, fundamentally, just as fast on both graphics cards. Again, this is an entry-level rendering job, though. What happens when we crank things up from weaksauce to hot sauce?

Paladin, directed by John Allardice, was distributed by Adobe during the CS5 launch to showcase what the software can do. It’s much more effects-heavy than our in-house benchmark, setting it up as a wonderful worst-case scenario for Hollywood-quality rendering jobs.

The impact of GPU-based acceleration here is phenomenal. Premiere Pro 5.0.2 added support for the Quadro 5000, but you don’t necessarily need one of the supported cards to accelerate the Mercury Playback Engine. Check out William Van Winkle’s story on Adobe CS5 for more on enabling hardware support with any CUDA-enabled GPU.

Create a new thread in the UK Article comments forum about this subject
This thread is closed for comments
3 comments
Comment from the forums
    Your comment
  • Anonymous
    Can you explain me why do have made renderings tests with this cards? They don't effect anything since this render engines have no CUDA or OPENCL.
    You could have put there an Intel crap and the results would be the same.
    1
  • nitro912gr
    What a big mistake in testing with cpu based methods!
    I work in Vue a lot and when the scene starts to count billions of polygons my poor 4850 is getting down to it's knees, when I try to move something on the scene, or move the camera. This is where these cards can make the difference.

    This is where you have to test these cards not in cpu based final renderings. Only in specific CUDA enabled renderers we can see the gpu to get in final render progress and only nvidia ones.

    The right question is how these cards manage with the frame rate in 4 views with thousands of objects an billions of polygons.

    No offense, but next time give the testing review to someone who actually have some experience in 3D, because first of all some things are making a conflict with preview and well informed articles about pro cards and second if you work with 3D you know what you are wanting for these cards and what they promise to do!

    Again no offense, just pointing out the obvious.
    0
  • nitro912gr
    What the hell is going on with all this spam? I have visited the article 3-4 times to check the new answers and all of them are spam spam spam...
    0