There's a few dimensions you can look at for gpu load. Probably the easiest indirect metric to watch for gpu load is power usage.<p>But if you really care about this, you should actually profile your application. nsight systems makes this pretty simple to do. Dunno how many actually care about having a TUI.
Power is useful as a second-order metric and can help catch drastic underutilization, but it has similar problems to SM Active (DCGM) -- it tends to overestimate utilization and doesn't distinguish between useful compute and memory traffic. It's very possible to be in a memory-bound workload with high power even though underutilizing compute utilization. Our goal was to separate these bottlenecks out so there's more visibility into where to optimize.<p>On nsys, agreed it's great, but we wanted something that could run continuously instead of an offline analysis tool. We think there's room for both to be useful.
You mention rocm-smi in your blog post, but you don't actually support AMD gpus?
We just track power utilization.
One small suggestion: add more GPU stats to your tool.<p>At the moment (v0.1.3) it <i>is</i> more helpful for compute visualization but keeping track of memory usage/processes/temperature/fan speed/etc. prevent this from becoming a full-on drop-in replacement for `nvidia-smi` for me.
Hi, many thx, does the os can run on nvidia jetson and orin? Or just for server gpu?
Currently just server GPU, but theoretically it should be easy to link against the ARM64 CUDA libraries for Jetson/Orin. The only challenge would be to check if it supports all the metrics we're sampling, though anything Ampere or newer should have reasonable support.
[dead]
[dead]
[dead]