RADEONTOP(1)

📦 version 1.4, in alpine 3.24, arch rolling, debian bookworm, debian trixie, epel 9, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

💖 RADEONTOP(1) 💖

okay bestie, welcome to RADEONTOP(1) — section 1 of the manual, the one that lives in your terminal and tells you what your GPU is actually doing with its life. this is the whole page, no skips, no gatekeeping. let's get into it 🫶

✨ NAME ✨

radeontop — the tool that shows you your GPU utilization. that's it, that's the whole vibe. 👑

🌸 SYNOPSIS 🌸

radeontop [-chmv] [-b bus] [-d file] [-l limit] [-i secs] [-p device]
[-t ticks]

that's the shape of it, babes. all those little flags? we're gonna go through every single one. no cap. 💅

🦋 DESCRIPTION 🦋

RadeonTop shows you the utilization of your GPU — both in general and by blocks. so like, not just "your card is busy," but which parts of your card are busy. main character energy from a monitoring tool, honestly. 😭

Supported cards are R600 and up. if your card is older than that... bestie, I'm so sorry, this isn't the one. 🙈

🎀 OPTIONS 🎀

one bullet per flag, all of them, exactly as written. let's go. ⭐

  • -b, --bus bus — got multiple cards in your rig? slay, use this to pick the specific one you wanna spy on. so if your lspci output is like 01:00.0 VGA compatible controller, then bus would be 1. just the 1, not the whole string. ikyk. 🔥
  • -c, --color — turns on colorized output. yes, your terminal deserves to be pretty. 🌈
  • -d, --dump file — instead of showing the data on screen, it dumps it into file. use - for stdout (because of course). and here's the cute part: the file gets appended to, so it's totally safe to specify the same filename for consecutive runs. nothing gets overwritten, you're fine. 🫶
heads up: use SIGTERM or SIGINT for graceful termination. graceful. we love a clean exit. ✨
  • -h, --help — displays help. the classic. when in doubt, ask for help. 💖
  • -i, --dump-interval seconds — wait N seconds between each chunk of data output. pacing yourself, queen. 🧚
  • -l, --limit limit — quit after dumping limit lines. ⚠️ this one is only valid in dump mode, so don't try it otherwise. the default behaviour is to dump until you terminate it; use SIGTERM or SIGINT for graceful termination. 🎀
  • -m, --mem — forces the use of the /dev/mem path, in case autodetection fails on you. genuinely useful for the proprietary driver. sometimes you just gotta tell it where to look. 👀
  • -p, --path device — opens the DRM device node specified by the device path. usually it's chilling at /dev/dri/card0 or /dev/drm0. and listen: if you use this option, then --bus and --mem get ignored. like, completely. so don't be surprised. 💀
  • -t, --ticks ticks — how many times per second to sample the data. default is 120. higher numbers mean more accurate output but also more overhead. the eternal tradeoff, fr fr. ⚖️
  • -v, --version — displays the program version. 💜

🌟 INTERACTIVE COMMANDS 🌟

yes bestie, you can type at it while it's running. very hands-on. 🎮

  • C, c — toggle colorized output. on. off. on. off. iconic. 💅
  • Q, q — quit. goodbye, farewell, exit stage left. 👋

🌈 RESOURCES 🌈

go look at http://github.com/clbr/radeontop for more. that's the link, that's the resource. 🍓

and that's the whole page, bestie!! you made it to the end, so proud of you 🥹

this was RADEONTOP(1), dated 09/30/2019, and yeah the manual name is right there in the title because we keep it real around here. now go check your GPU utilization, you gorgeous nerd. 💖✨🦋

📦 where this page comes from