Page 1 of 6 123 ... LastLast
Results 1 to 10 of 57

Thread: A Fresh Look At The AMD Radeon Gallium3D Performance

  1. #1
    Join Date
    Jan 2007
    Posts
    14,658

    Default A Fresh Look At The AMD Radeon Gallium3D Performance

    Phoronix: A Fresh Look At The AMD Radeon Gallium3D Performance

    As noted earlier in the week, the open-source AMD Radeon "R600g" driver that supports 3D acceleration on Radeon HD 2000 series graphics cards through the latest Radeon HD 6000 and Fusion graphics processors, is becoming quite fit. The driver is nearing a point of stability, is mature enough for most desktop users, and it is beginning to receive some performance optimizations and other improvements. Thanks to this recent work, plus the ongoing development of the Linux 3.0 kernel, here is a fresh set of AMD Gallium3D Linux driver benchmarks.

    http://www.phoronix.com/vr.php?view=16110

  2. #2
    Join Date
    May 2010
    Posts
    135

    Default

    Can you include things like KWin and Compiz performance? Those are still pretty important, though as things keep getting faster, they will end up being non-interesting after a few years.

  3. #3
    Join Date
    Aug 2007
    Posts
    6,615

    Default

    This is a much better benchmark comparison than the ones before. Disabling SwapbuffersWait has usally the most impact of benchmarks. I did not test the impact of the other option used. The problem with SwapbuffersWait is when a game runs in the 20-25 fps range, then tearing is really extreme, like Trine, in that case i usually enable it. But for benchmarking you definitely should turn it off. Maybe test with installelled libtxc_dxtn and enabled texture-float unigine heaven, but of course in that case you need to disable tesselation in the benchmark.

  4. #4
    Join Date
    Aug 2008
    Posts
    224

    Default

    Excellent news and excellent article!

  5. #5
    Join Date
    Oct 2008
    Posts
    3,105

    Default

    Quote Originally Posted by Kano View Post
    This is a much better benchmark comparison than the ones before. Disabling SwapbuffersWait has usally the most impact of benchmarks. I did not test the impact of the other option used. The problem with SwapbuffersWait is when a game runs in the 20-25 fps range, then tearing is really extreme, like Trine, in that case i usually enable it. But for benchmarking you definitely should turn it off. Maybe test with installelled libtxc_dxtn and enabled texture-float unigine heaven, but of course in that case you need to disable tesselation in the benchmark.
    Agreed. These benchmarks with everything over 100 fps are of questionable use, but overall this was a much better set of tests than usual. I really wish Michael would benchmark some more challenging apps, like Doom3, Portal, etc. in addition to the standard Quake 3 engines.

  6. #6
    Join Date
    Jan 2009
    Posts
    1,658

    Default

    would it be easy for someone to explain why we don't have consistent performance across resolutions ?? (at least Catalyst seems to fluctuate less than the Open solutions)

  7. #7

    Default

    Quote Originally Posted by smitty3268 View Post
    I really wish Michael would benchmark some more challenging apps
    Most still don't run well on Mesa / G3D.... For those that do, submit a Phoronix Test Suite test profile for them if you want to see them used and then they get picked up right away for use in articles.

  8. #8
    Join Date
    Mar 2010
    Posts
    27

    Default

    how about benching the blender view-port performance in different modes?
    this is something you actually use compared to benches like lightsmark

  9. #9

    Default

    Quote Originally Posted by EvilTwin View Post
    how about benching the blender view-port performance in different modes?
    this is something you actually use compared to benches like lightsmark
    Submit a test profile and it will be included...

  10. #10
    Join Date
    May 2008
    Posts
    99

    Default nice

    Ok, now we are getting somewhere....

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •