radeontop VS cargo-binstall

Linux - with Terminal, install Radeontop (https://github.com/clbr/radeontop) with sudo apt install radeontop , start with radeontop . It's not cutting edge graphics but it works for me as a tool. I'm experimenting with ai apps in Linux and I need to know what my gpu is doing.

I am currently working on a tool that will be the successor to radeontop.

There's radeontop, which can show some information. That's the only thing I'm aware of.

Take a look at radeontop: https://github.com/clbr/radeontop

https://github.com/clbr/radeontop shows 70-85% usage when playing this 4k60FPS video https://www.youtube.com/watch?v=LXb3EKWsInQ

No, it doesn't show encode/decode. Some people on this subreddit will tell you it does for whatever reason like they do every time I bring this up, they clearly never used it or something, but no it does not. There is no easy way to see it like on Intel and Nvidia.

radeon-top

AMD has like 2 or 3 different drivers on nix. The default one is the open source driver. If you see the desktop, it's working. Run a game, should perform decently. You don't see the GPU in performance monitor. That's because GPU metrics aren't standard. You'd need other tools to see GPU metrics.

It can get worse depending on what specific aspect of the GPU is being used. Want to check if your computer is properly using hardware encoding/decoding? Well, you're in luck (with CLI tools), nvidia-smi dmon and intel_gpu_top are really good. Unless you use AMD that is, since radeontop still doesn't have a way to expose GPU encoding/decoding.

Unfortunately not really usable in production (for me) until https://github.com/cargo-bins/cargo-binstall/issues/1 is fixed :( Really much looking forward to it though, as I think it's a great addition to the Rust ecosystem!

Oh looks like cargo-binstall is currently broken (https://github.com/cargo-bins/cargo-binstall/issues/1094)

Unfortunately, I ended up running into an issue with the zip support, but I'll come back to it once this is fixed: https://github.com/cargo-bins/cargo-binstall/issues/1080

I've encountered a strange lifetime error when developing new features in cargo-binstall:

Once you feel like releasing it, could you please add binstall support?

I think in a similar vein there is cargo-binstall that is a cargo install alternative that attempts to use pre-built binary artifacts when possible

I hope ld64 and lld add supports for plugin-opt I'm trying to enable cross-lang-lto on MacOS but failed due to -plugin-opt not supported.

You can use cargo-binstall --install-path to install binaries to custom locations.

If you happen to install a lot of things with cargo, check out cargo-binstall: https://github.com/cargo-bins/cargo-binstall

It'll fetch the binary release from the repo so you don't have to compile it yourself.

I'd recommend to use cargo-binstall, which can download pre-built artifacts from github release.