Announcement

Collapse
No announcement yet.

13-Way R600/RadeonSI GPU Comparison With Mesa 10.1 On Ubuntu 14.04

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • 13-Way R600/RadeonSI GPU Comparison With Mesa 10.1 On Ubuntu 14.04

    Phoronix: 13-Way R600/RadeonSI GPU Comparison With Mesa 10.1 On Ubuntu 14.04

    With the imminent release of Mesa 10.1 and Ubuntu 14.04 LTS landing this updated open-source 3D graphics stack at the last minute, here are some benchmarks of this preliminary open-source GPU driver stack of Ubuntu 14.04 with Mesa 10.1 and the Linux 3.13 kernel. With Mesa 10.1 there is now also Unigine Heaven & Valley benchmarks that are now compatible with the Radeon Gallium3D drivers.

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

  • curaga
    replied
    Originally posted by asdfblah View Post
    vblank_mode=0 env vars to .. disable vsync...
    PTS does that one automatically.

    Leave a comment:


  • asdfblah
    replied
    Originally posted by asdfblah View Post
    @Michael
    Could you please test Ubuntu 13.10 with oibaf's PPA + this PPA: https://launchpad.net/~nzatkovich/+a...eediergraphics + latest linux 3.14 RC, + performance CPU governor, + radeon.dpm=1 for all the cards?
    It would be interesting to have a look at the current state of the drivers, and to compare them to fglrx under the same conditions (to see if CPU governor really is a factor, and to know if the FOSS driver is at the same performance level under this conditions)
    and also, tiling enbled + R600_DEBUG=hyperz + vblank_mode=0 env vars to enable optimizations and disable vsync...

    Leave a comment:


  • asdfblah
    replied
    @Michael
    Could you please test Ubuntu 13.10 with oibaf's PPA + this PPA: https://launchpad.net/~nzatkovich/+a...eediergraphics + latest linux 3.14 RC, + performance CPU governor, + radeon.dpm=1 for all the cards?
    It would be interesting to have a look at the current state of the drivers, and to compare them to fglrx under the same conditions (to see if CPU governor really is a factor, and to know if the FOSS driver is at the same performance level under this conditions)

    Leave a comment:


  • agd5f
    replied
    Originally posted by FutureSuture View Post
    Would using this fix any issues that the GCN 1.1 cards are having?
    No. the fixes are known. Use a 3.14 kernel and enable tiling in your xorg.conf

    Leave a comment:


  • FutureSuture
    replied
    Would using this fix any issues that the GCN 1.1 cards are having?

    Leave a comment:


  • Azpegath
    replied
    Originally posted by agd5f View Post
    With kernel 3.13, dpm is not enabled by default so CIK parts are running at their boot up clocks which are like a 100Mhz. 3.14 enables dpm by default on those asics. Additionally, tiling is not yet enabled by default on CIK parts. That should be enabled in the next ddx release.
    Sounds like Michael should re-run the tests with DPM and Tiling enabled.

    Leave a comment:


  • agd5f
    replied
    With kernel 3.13, dpm is not enabled by default so CIK parts are running at their boot up clocks which are like a 100Mhz. 3.14 enables dpm by default on those asics. Additionally, tiling is not yet enabled by default on CIK parts. That should be enabled in the next ddx release.

    Leave a comment:


  • curaga
    replied
    True, but shader optimizations should have little to no effect here. It's a very simple triangle, completely memory-bound. It's as if tiling was not enabled for Cayman, which could explain that ~50% discrepancy.

    Leave a comment:


  • peapa
    replied
    Originally posted by curaga View Post
    Cayman is indeed behaving weirdly, in should win in the tri test for example, having ~20% more bandwidth than a 6870.
    Cayman is VLIW4 hardware and since quite some time benchmarks show that it's not as optimized as VLIW5 with the open source stack.

    Leave a comment:

Working...
X