-
-
Notifications
You must be signed in to change notification settings - Fork 48
Introduce per process GPU usage #490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
May I ask you to propose a PR that works for you? I'm wondering what would be the best solution to choose the right engine to read. We need to read driver name from GPU class and based on that do the right choice. |
|
@stsdc I've been looking around, but the kernel docs are not the clearest on this. Instead, its easier to simply read the output from various files in fdinfo on various setups. Doing this, there only shows up two engines and that the driver is Here is info from a heavy gpu process: The I'm assuming that engine is called the There also appears to be a pro version of the driver, but I don't have that right now. I think I can get it by installing ROCm, but I'm not sure I'd need it for a while, and it is a bit of a hassle. Might be easier to rent a server briefly to get this gpu information. |
|
@Tbusk also check what Resources does: https://github.com/nokyan/resources/blob/main/lib/process_data/src/gpu_usage.rs |
|
Just checked what my nvidia 3000 series laptop is running during a stress test (which works on the PR) towards both my onboard graphics and my nvidia card: I have
Also the only addition needed to make it work on my amd machine is to add a fall-though case above your case in the switch in So case "drm-engine-gfx":
case "drm-engine-render":I can do a pr if you want. |
|
I'll appreciate if you'll make a PR. |
After looking at it a little, the value of Example of a handful of minutes difference in a stress test: |
|
@Tbusk please check if it works for you now |



Needs testing on hardware.