DirectCompute, OpenCL, and the Future of CAL

As a journalist, GPGPU stuff is one of the more frustrating things to cover. The concept is great, but the execution makes it difficult to accurately cover, exacerbated by the fact that until now AMD and NVIDIA each had separate APIs. OpenCL and DirectCompute will unify things, but software will be slow to arrive.

As it stands, neither AMD nor NVIDIA have a complete OpenCL implementation that's shipping to end-users for Windows or Linux. NVIDIA has OpenCL working on the 8-series and later on Mac OS X Snow Leopard, and AMD has it working under the same OS for the 4800 series, but for obvious reasons we can’t test a 5870 in a Mac. As such it won’t be until later this year that we see either side get OpenCL up and running under Windows. Both NVIDIA and AMD have development versions that they're letting developers play with, and both have submitted implementations to Khronos, so hopefully we’ll have something soon.

It’s also worth noting that OpenCL is based around DirectX 10 hardware, so even after someone finally ships an implementation we’re likely to see a new version in short order. AMD is already talking about OpenCL 1.1, which would add support for the hardware features that they have from DirectX 11, such as append/consume buffers and atomic operations.

DirectCompute is in comparatively better shape. NVIDIA already supports it on their DX10 hardware, and the beta drivers we’re using for the 5870 support it on the 5000 series. The missing link at this point is AMD’s DX10 hardware; even the beta drivers we’re using don’t support it on the 2000, 3000, or 4000 series. From what we hear the final Catalyst 9.10 drivers will deliver this feature.

Going forward, one specific issue for DirectCompute development will be that there are three levels of DirectCompute, derived from DX10 (4.0), DX10.1 (4.1), and DX11 (5.0) hardware. The higher the version the more advanced the features, with DirectCompute 5.0 in particular being a big jump as it’s the first hardware generation designed with DirectCompute in mind. Among other notable differences, it’s the first version to offer double precision floating point support and atomic operations.

AMD is convinced that developers should and will target DirectCompute 5.0 due to its feature set, but we’re not sold on the idea. To say that there’s a “lot” of DX10 hardware out there is a gross understatement, and all of that hardware is capable of supporting at a minimum DirectCompute 4.0. Certainly DirectCompute 5.0 is the better API to use, but the first developers testing the waters may end up starting with DirectCompute 4.0. Releasing something written in DirectCompute 5.0 right now won’t do developers much good at the moment due to the low quantity of hardware out there that can support it.

With that in mind, there’s not much of a software situation to speak about when it comes to DirectCompute right now. Cyberlink demoed a version of PowerDirector using DirectCompute for rendering effects, but it’s the same story as most DX11 games: later this year. For AMD there isn’t as much of an incentive to push non-game software as fast or as hard as DX11 games, so we’re expecting any non-game software utilizing DirectCompute to be slow to materialize.

Given that DirectCompute is the only common GPGPU API that is currently working on both vendors’ cards, we wanted to try to use it as the basis of a proper GPGPU comparison. We did get something that would accomplish the task, unfortunately it was an NVIDIA tech demo. We have decided to run it anyhow as it’s quite literally the only thing we have right now that uses DirectCompute, but please take an appropriately sized quantity of salt – it’s not really a fair test.

NVIDIA’s ocean demo is a fairly simple proof of concept program that uses DirectCompute to run Fast Fourier transforms directly on the GPU for better performance. The FFTs in turn are used to generate the wave data, forming the wave action seen on screen as part of the ocean. This is a DirectCompute 4.0 program, as it’s intended to run on NVIDIA’s DX10 hardware.

The 5870 has no problem running the program, and in spite of whatever home field advantage that may exist for NVIDIA it easily outperforms the GTX 285. Things get a little more crazy once we start using SLI/Crossfire; the 5870 picks up speed, but the GTX 295 ends up being slower than the GTX 285. As it’s only a tech demo this shouldn’t be dwelt on too much beyond the fact that it’s proof that DirectCompute is indeed working on the 5800 series.

Wrapping things up, one of the last GPGPU projects AMD presented at their press event was a GPU implementation of Bullet Physics, an open source physics simulation library. Although they’ll never admit it, AMD is probably getting tired of being beaten over the head by NVIDIA and PhysX; Bullet Physics is AMD’s proof that they can do physics too. However we don’t expect it to go anywhere given its very low penetration in existing games and the amount of trouble NVIDIA has had in getting developers to use anything besides Havok. Our expectations for GPGPU physics remains the same: the unification will come from a middleware vendor selling a commercial physics package. If it’s not Havok, then it will be someone else.

Finally, while AMD is hitting the ground running for OpenCL and DirectCompute, their older APIs are being left behind as AMD has chosen to focus all future efforts on OpenCL and DirectCompute. Brook+, AMD’s high level language, has been put out to pasture as a Sourceforge project. Compute Abstract Layer (CAL) lives on since it’s what AMD’s OpenCL support is built upon, however it’s not going to see any further public development with the interface frozen at the current 1.4 standard. AMD is discouraging any CAL development in favor of OpenCL, although it’s likely the High Performance Computing (HPC) crowd will continue to use it in conjunction with AMD’s FireStream cards to squeeze every bit of performance out of AMD’s hardware.

The First DirectX 11 Games Eyefinity
Comments Locked

327 Comments

View All Comments

  • Zool - Friday, September 25, 2009 - link

    "The GT300 is going to blow this 5870 away - the stats themselves show it, and betting otherwise is a bad joke, and if sense is still about, you know it as well."
    If not than it would be a sad day for nvidia after more than 2 years of nothing.
    But the 5870 can still blow away any other card around. With DX11 fixed tesselators in pipeline and compute shader postprocessing (which will finaly tax the 1600 stream procesors)it will look much better than curent dx9. The main advantage of this card is the dx11 which of course nvidia doesnt hawe. And maybe the dewelopers will finaly optimize for the ati vector architecture if there isnt any other way meant to be played(payed) :).
    Actualy nvidia couldnt shrink the last gen to 40nm with its odd high frequency scalar shaders (which means much more leakage) so i wouldent expect much more from nvidia than double the stats and make dx11 either.
  • SiliconDoc - Friday, September 25, 2009 - link

    Here more new NVidia cards, so the fasle 2 years complaint is fixzling fast.
    Why this hasn't been mentioned here at anadtech yet I'm not sure, but of course...

    http://www.fudzilla.com/content/view/15698/1/">http://www.fudzilla.com/content/view/15698/1/

    Gigabyte jumps the gun with 40nm

    According to our info, Nvidia's GT 220, 40nm GT216-300 GPU, will be officially announced in about three weeks time.

    The Gigabyte GT 220 works at 720MHz for the core and comes with 1GB of GDDR3 memory clocked at 1600MHz and paired up with a 128-bit memory interface. It has 48 stream processors with a shader clock set at 1568MHz.
    --
    See, there's a picture as well. So, it's not like nothing has been going on. It's also not "a panicky response to regain attention" - it is the natural progression of movement to newer cores and smaller nm processes, and those things take time, but NOT the two years plus ideas that spread around....
  • SiliconDoc - Friday, September 25, 2009 - link

    The GT200 was released on June 16th and June17th, 2008, definitely not more than 2 years ago, but less.
    The 285 (nm die shrink) on January 15th, 2009, less than 1 year ago.

    The 250 on March 3rd this year, though I wouldn't argue you not wanting to count that.

    I really don't think I should have to state that you are so far off the mark, it is you, not I, that might heal with correction.

    Next, others here, the article itself, and the ati fans themselves won't even claim the 5870 blows away every other card, so that statement you made is wrong, as well.
    You could say every other single core card - no problem.
    Let's hope the game scenes do look much better, that would be wonderful, and a fine selling point for W7 and DX11 (and this casrd if it is, or remains, the sole producer of your claim).
    I suggest you check around, the DX11 patch for Battleforge is out, so maybe you can find confirmation of your "better looking" games.

    " Actualy nvidia couldnt shrink the last gen to 40nm with its odd high frequency scalar shaders "
    I believe that is also wrong, as they are doing so for mobile.
    What is true is ATI was the ginea pig for 40nm, and you see, their yeilds are poor, while NVidia, breaking in later, has had good yeilds on the GT300, as stated by - Nvidia directly, after ATI made up and spread lies about 9 or less per wafer. (that link is here, I already posted it)
    ---
    If Nvidia's card doubles performance of the 285, twice the frames at the same reso and settings, I will be surprised, but the talk is, that or more. The stats leaked make that a possibility. The new MIMD may be something else, I read 6x-15x the old performance in certain core areas.
    What Nvidia is getting ready to release is actually EXCITING, is easily described as revolutionary for videocards, so yes, a flop would be a very sad day for all of us. I find it highly unlikely, near impossible, the silicon is already being produced.
    The only question yet is how much better.
  • Zool - Friday, September 25, 2009 - link

    I want to note also that the 5870 is hard to find which means the 40nm tsmc is still far from the last gen 55nm. After they manage it to get on the 4800 level the prices will be different. And maybe the gt300 is still far away.
  • mapesdhs - Friday, September 25, 2009 - link


    Is there any posting moderation here? Some of the flame/troll posts
    are getting ridiculous. The same thing is happening on toms these days.

    Jarred, best not to reply IMO. I don't think you're ever going to get
    a logical response. Such posts are not made with the intent of having
    a rational discussion. Remember, as Bradbury once said, it's a sad
    fact of nature that half the population have got to be below average. :D

    Ian.


  • Zool - Friday, September 25, 2009 - link

    I would like to see some more tests on power load. Actualy i dont think there are too many people with 2560*1600 displays. There are still plenty people with much lower resolutions like 1680*1050 and play with max imagequality. With VSync on if u reduce 200fps to 60fps u get much less gpu temps and also power load.(things like furmark are miles away from real world) On LCD there is no need to turn it off just if u benchmark and want more fps. I would like to see more power load tests with diferent resolutions and Vsync on.(And of course not with crysis)
    Also some antialiasing tests, the adaptive antialiasing on 5800 is now much faster i read.And the FSAA is of course blurry, it was always so. If u render the image in 5120*3200 on your 2560*1600 display and than it combines the quad pixels it will seems like its litle washed out. Also in those resolution even the highress textures will begin to pixalate even in closeup so the combined quad pixels wont resemble the original. Without higher details in game the FSAA in high resolution will just smooth the image even more. Actualy it always worked this way even on my gf4800.

  • SiliconDoc - Friday, September 25, 2009 - link

    PS - a good friend of mine has an ATI HD2900 pro with 320 shaders (a strange one not generally listed anywhere) that he bought around the time I was showing him around the egg cards and I bought an ATI card as well.
    Well, he's a flight simmer, and it has done quite well for him for a about a year, although in his former Dell board it was LOCKED at 500mhz 503mem 2d and 3d, no matter what utility was tried, and the only driver that worked was the CD that came with it.
    Next on a 570 sli board he got a bit of relief, an with 35 various installs or so, he could sometimes get 3d clocks to work.
    Even with all that, it performed quite admirably for the strange FS9 not being an NVidia card.
    Just the other day, on his new P45 triple pci-e slot, after 1-2 months running, another friend suggested he give OCCT a go, and he asked what is good for stability (since he made 1600fsb and an impressive E4500 (conroe) 200x11/2200 stock to a 400x8/ 3200mhz processor overclock for the past week or two). "Ten minutes is ok an hour is great" was the response.
    Well, that HD2900pro and OCCT didn't like eachother much either - and DOWN went the system, 30 seconds in, cooking that power supply !
    --- LOL ---
    Now that just goes to show you that hiding this problem with the 4870 and 4890 for so many months, not a peep here... is just not good for end users...
    ---
    Thanks a lot tight lipped "nothing is wrong with ATI cards" red fans. Just wonderful.
    ---
    He had another PS and everything else is OK

    , and to be quite honest and frank and fair as I near always am, that HD2900pro still does pretty darn good for his flight simming ( and a few FPS we all play sometimes) and he has upgraded EVERYTHING else already at least once, so on that card, well done for ATI. (well depsite the drivcer issues, 3d mhz issues, etc)
    Oh, and he also has a VERY NICE 'oc on it now(P45 board) - from 600/800 core/mem 3D to 800/1000, and 2d is 500/503, so that's quite impressive.
  • SiliconDoc - Wednesday, September 30, 2009 - link

    Ahh, isn't that typical, the 3 or 4 commenters raving for ati "go dead silent" on this furmark and OCCT issue.
    --
    "It's ok we never mentioned it for a year plus as we guarded our red fan inner child."
    (Ed. note: We "heard" nvidia has a similar implementation")
    WHATEVER THAT MEANS !
    ---
    I just saw (somewhere else) another red fanatic bloviating about his 5870 only getting up to 76C in Furmark. ROFLMAO
    --
    Aww, the poor schmuck didn't know the VRM's were getting cut back and it was getting throttled from the new "don't have a heat explosion" tiny wattage crammed hot running ati core.
  • SiliconDoc - Friday, September 25, 2009 - link

    Well you brought to mind another sore spot for me.
    In the article, when the 4870 and 4890 FAIL furmark and OCCT, we are suddenly told, after this many MONTHS, that a blocking implementation in ati driver version 9.2 was put forth by ATI, so their cards wouldn't blow to bits on furmark and OCCT.
    I for one find that ABSOLUTELY AMAZING that this important information took this long to actually surface at red central - or rather, I find it all too expected, given the glaring bias, ever present.
    Now, the REASON this information finally came forth, other thanb the epic fail, is BECAUSE the 5870 has a "new technology" and no red fan site can possibly pass up bragging about something new in a red core.
    So the brag goes on, how protection bits in the 5870 core THROTTLE BACK the VRM's when heat issues arise, hence allowing for cheap VRM's & or heat dissipation issues to divert disaster.
    That's wonderful, we finally find out about ANOTHER 4870 4980 HEAT ISSUE, and driver hack by ATI, and a failure to RUN THE COMMON BENCHMARKS we have all used, this late in the game.
    I do have to say, the closed mouthed rabid foam contained red fans are to appluaded for their collective silence over this course of time.
    Now, further bias revealed in tha article - the EDITOR makes sure to chime in, and notes ~"we have heard Nvidia has a similar thing".
    What exactly that similar thing is, and whom the Editor supposedly heard it from, is never made clear.
    Nonetheless, it is a hearty excuse and edit for, and in favor of, EXCUSING ATI's FAILURES.

    Nonetheless, ALL the nvidia cards passed all the tests, and were 75% in number to the good cooler than the ATI's that were- ATI all at 88C-90C, but, of course, the review said blandly in a whitewash, blaming BOTH competitors nvidia and ati - "temps were all over the place" (on load).
    (The winning card GTX295 @ 90C, and 8800GT noted 92C *at MUCH reduced case heat and power consumption, hence INVALID as comparison)
    Although certain to mention the GT8800 at 92C, no mention of the 66C GTX250 or GTX260 winners, just the GTX275 @ 75C, since that was less of a MAJOR EMBARRASSMENT for the ATI heat load monsters !
    Now THERE'S A REAL MONSTER - AND THAT'S ALL OF THE ATI CARDS TESTED IN THIS REVIEW ! Not just the winning nvidia, while the others that matter (can beat 5870 in sli or otherwise) hung 24C to 14C lower under load.
    So, after all that, we have ANOTHER BIAS, GLARING BIAS - the review states " there are no games we know of, nor any we could find, that cause this 5870 heat VRM throttling to occur".
    In other words, we are to believe, it was done in the core, just for Furmark and OCCT, or, that it was done as precaution and would NEVER come into play, yes, rest assured, it just won't HAPPEN in the midst of a heavy firefight when your trigger finger is going 1,000mph...
    So, I found that just CLASSIC for this place. Here is another massive heat issue, revealed for the first time for 4870 and 4890 months and months and months late, then the 5870 is given THE GOLDEN EXCUSE and massive pass, as that heat reducing VRM cooling voltage cutting framerate lowering safety feature "just won't kick in on any games".
    ROFL
    I just can't help it, it's just so dang typical.
  • DigitalFreak - Friday, September 25, 2009 - link

    Looks like SnakeOil has yet ANOTHER account.

Log in

Don't have an account? Sign up now