1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

Radeon VRAM Optimizations Coming, But Help Is Needed

AMD

Published on 11 January 2014 05:00 PM EST
Written by Lauri Kasanen in AMD
129 Comments

Got a workload that runs badly on the r600g Radeon Gallium3D driver? You can help fix it! Optimizations are coming to the open-source Radeon Linux driver for video memory usage.

I'm currently working on my thesis (Software Engineering), studying the VRAM behavior of radeon. For r600g, much of the remaining gap to fglrx can be explained by less than optimal VRAM use. There's fragmentation, and there's ping-pong of buffers to and from VRAM.

You can help by recording a trace of the app's memory use. If you use Oibaf's PPA, you're set; if you build Mesa yourself, please apply the patches from the stats6 branch.

Run the app with the R600_DEBUG environment variable set to enable tracing (bostats), for example "R600_DEBUG=bostats dota2". The trace will be written to /tmp/bostats.[pid].dota2.

Once a few minutes of gameplay have been captured, exit the game. Please compress this file with XZ, upload somewhere (dropbox, anonfiles, bayfiles, etc) and e-mail me the link to cand at gmx dot com.

Please include a description of the app, settings used, and the version of the app. If it's a private application, please specify that too.

I would really appreciate traces from commercial apps, both native and those used via Wine. I can record most open-source apps myself, but if you have a specific case (for example, Xonotic with specific settings only) that runs badly, please record that.

Notes:

- The machine doesn't have to be the slow one. For example, if WoW is slow on your integrated card, but fast on a discrete, feel free to record on the discrete. The trace will be the same, assuming settings are the same.
- There is nothing confidential in the trace, so any private apps are safe to record.
- If your /tmp is in RAM, a big trace might fill it -- use TMPDIR=/home/foo etc to specify a dir on storage.
- While radeonsi could be used in theory, it has not been tested, and traces from it are incorrect (they lack much of the cpu statistics).

Thanks to Lauri Kasanen for reaching out to us so that Phoronix readers can help him in having a successful thesis and his continued work on improving the open-source Radeon Linux graphics driver. For any questions, please drop by the forums.

Latest Linux Hardware Reviews
  1. The Power Consumption & Efficiency Of Open-Source GPU Drivers
  2. AMD R600g/RadeonSI Performance On Linux 3.16 With Mesa 10.3-devel
  3. Intel Pentium G3258 On Linux
  4. SilverStone Precision PS10
Latest Linux Articles
  1. Nouveau vs. Radeon vs. Intel Tests On Linux 3.16, Mesa 10.3-devel
  2. KVM Benchmarks On Ubuntu 14.10
  3. X.Org Server 1.16 Officially Released With Terrific Features
  4. Ubuntu With Linux 3.16 Smashes OS X 10.9.4 On The MacBook Air
Latest Linux News
  1. Git 2.1 To Further Mainline Windows Support Patches
  2. Debian 8.0 Jessie Is Settling For Linux 3.16
  3. Meson: A Next-Gen Build System Showing Promise
  4. Linux 3.16-rc7 Calms Things Down For The Linux 3.16 Kernel
  5. Open-Source AMD Users Report Hawaii GPU Acceleration Is Working
  6. Linus Torvalds On GCC 4.9: Pure & Utter Crap
  7. Cauldron 2014: GCC & LLVM Will Look To Collaborate More
  8. GCC Receives ACM Programming Languages Software Award
  9. KDE 4.14 Beta 3 Released
  10. A New Video Has Us Real Excited About The New UT For Linux
Latest Forum Discussions
  1. ASRock AM1H-ITX: One Of The Best AM1 Mini-ITX Motherboards
  2. Debian + radeonsi
  3. Open-source drivers on ATI R7 260X
  4. Updated and Optimized Ubuntu Free Graphics Drivers
  5. Table test
  6. How To Setup Radeon DPM On Ubuntu Linux
  7. New build, first Linux PC, what could go wrong? ;)
  8. AMD "Hawaii" Open-Source GPU Acceleration Still Not Working Right