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 Benchmarking Platform
Phoromatic Test Orchestration

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 News
  1. HiSense Chromebook Benchmarks When Running Ubuntu Linux
  2. Mandriva Linux Was Allegedly Brought Down By Employee Lawsuits
  3. GNOME 3.17.2 Is Released As The Latest Look Towards GNOME 3.18
  4. Phoronix Turns 11 Years Old Next Week: How Should We Celebrate?
  5. Ubuntu Community Council Reaffirms Its Decision Against Kubuntu's Leader
  6. Future Plans For Changing Fedora's Installer
  7. Confusion Mounts Over Wayland's Actual License
  8. GNOME's Mutter Now Supports Drag-n-Drop To/From Wayland & X11
  9. Wine 1.7.44 Works On More 64-bit ARM Support
  10. Phoronix Test Suite 5.8 Milestone 5 Brings Near Final "Belev" Experience
Latest Articles & Reviews
  1. Btrfs RAID 0/1/5/6/10 Five-Disk Benchmarks On Linux 4.1
  2. Opening The Gates To Our Daily Open-Source Linux Benchmark Results
  3. The Latest Features For Linux Performance Management + Benchmark Monitoring
  4. Noctua NH-U12DX i4 + NF-F12
Most Viewed News This Week
  1. NVIDIA's Proprietary Driver Is Moving Closer With Kernel Mode-Setting
  2. Features Added To Mesa 10.6 For Open-Source GPU Drivers
  3. Ubuntu's LXD vs. KVM For The Linux Cloud
  4. Friction Building Around An Ubuntu Community Council Decision
  5. The Latest Linux Kernel Git Code Fixes The EXT4 RAID0 Corruption Problem
  6. The CompuLab Fitlet Is A Neat Little Linux PC With AMD SoC
  7. Linux 4.1-rc5 Kernel Released
  8. Russia's Baikal Chips End Up Going For A MIPS CPU