How to monitor AMD/ATI or Radeon GPU usage in Linux

Are you really looking for a way to monitor the usage of a discrete AMD/ATI or Radeon GPU? Okay, then you are in the right place. This guide will work for the open source drivers(mesa) and also with proprietary drivers(AMD Catalyst).

This tool measures memory usage and basically overall stress of your AMD GPU. I personally stumbled upon this tool while I was trying to make sure if my AMD GPU drivers are installed properly or not. And after I was sure that open source mesa drivers are installed I tested how well an AMD GPU work with open source drivers and then compared it with my integrated Intel HD 620 GPU. Check it out if it interests you.

There is not much to talk about this tool so let us get started with the real thing.

How to install radeontop

Step 1: Install ‘radeontop‘ on your distro. If you are using distros like Ubuntu, Fedora, Mint etc then most likely radeontop is already available in the repos.

# Install radeontop on your distro via repos.

$ sudo apt-get install radeontop


$ sudo rpm install radeontop


follow instructions of this page: build radeontop

How to use radeontop:

Step 2: launch radeontop with root permissions and monitor the usage.

$ sudo radeontop

If nothing is moving around in the display then it is most likely because your GPU is not being used(here is how you can launch apps via terminal using discrete GPU in Linux) or your drivers are not installed or working properly. If you see stats changing then this is it everything working fine.

radeontop status while running glmark2 benchmark in linux

This is how its gonna look in radeontop when your GPU is working. Values at the bottom show memory usage of your GPU. In my case, it is showing 13 MB used out of total 2048 MB memory.

So this is it for this article, hope this was helpful. Have a good day.

1 thought on “How to monitor AMD/ATI or Radeon GPU usage in Linux”

  1. on my fedora 30 system this constantly used one full core, even after exiting it with ctrl+c. killall radeontop fixed it.

    so check wether you experience the same bug, I didn’t notice for a few months… :/


Leave a Comment