Resources System Monitoring App For GNOME Now Displays NPU Usage

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • yump
    replied
    Originally posted by reba View Post
    - It wakes up the dGPU vom D3cold just to show there is nothing using it (you serious?! Check power state before doing stupid crap
    Thank you so much for noticing and mentioning this. It is very important and frequently overlooked how many ways of poking at a GPU's /sys/ files can cause it to consume 10+ watts.

    When I fixed this problem in my fan control script, it needed a state machine to monitor the utilization and switch into a hands-off mode if it was consistently low, and the hands-off mode looks at nothing, not even utilization, except for the PCI power state file.

    Edit:

    Originally posted by QwertyChouskie View Post
    Yeah, that's a known issue (https://gitlab.com/mission-center-de...er/-/issues/30). Unfortunately, it's a tough one, as all the normal ways of querying the GPU wake it up. There's one possible method I know of that would probably work reasonably well for 99% of people (https://gitlab.com/mission-center-de...ote_1729912246) but it has not been implemented yet.
    That actually sounds way more robust than what I did, and it's apparently stateless. And that bug report collects more information about how not to wake a GPU in one place than I've ever found. Thanks!
    Last edited by yump; 15 December 2024, 05:33 AM.

    Leave a comment:


  • QwertyChouskie
    replied
    Originally posted by reba View Post

    Just tried it out of cusiosity and because they, at least, provide an AppImage.

    - But the interface feels sooooo sluggish
    - The animations just get in my way of seeing the information, scrolling is a pain and slow
    Weird, it should generally be pretty snappy as GTK4 is designed to be GPU-accelerated. Mind mentioning what hardware you are running it on?

    Originally posted by reba View Post
    - Mouse cursor is enlarged and not correct
    Pretty sure that's a GTK4 bug that should be fixed in the next version.

    Originally posted by reba View Post
    - Window icons are broken
    Might have to do with your setup? Maybe adwaita-icon-theme needs to be installed on your system? FWIW, the Flatpak and Snap should generally be more resilient towards differences in system configurations/missing packages.

    Originally posted by reba View Post
    - It wakes up the dGPU vom D3cold just to show there is nothing using it (you serious?! Check power state before doing stupid crap)
    Yeah, that's a known issue (https://gitlab.com/mission-center-de...er/-/issues/30). Unfortunately, it's a tough one, as all the normal ways of querying the GPU wake it up. There's one possible method I know of that would probably work reasonably well for 99% of people (https://gitlab.com/mission-center-de...ote_1729912246) but it has not been implemented yet.

    Originally posted by reba View Post
    - Not much information presented, especially on the running tasks page
    Originally posted by reba View Post
    - Overall not much information or information that is irrelevant because trivial
    I'd be curious to hear your suggestions on what additional information you would like to see.

    Leave a comment:


  • sophisticles
    replied
    Originally posted by coder View Post
    I really like AviDemux. It has builtin support for keyframe-only editing, which I've used to edit MPEG2-TS files without transcoding. That said, I really haven't gone very deep into its capabilities, so I can't say how it compares as a NLE, overall.
    If I ever came into a lot of money, I would reach out to the developers to offer to sponsor them to add support for the complete Intel and NVIDIA video stacks as well as support for ProRes encode.

    Originally posted by coder View Post
    On what, a Nvidia GPU? Which one and how fast was it?
    No, Ice Lake i5-1035G1 with iGPU.

    Definitely not real time, but this is an old processor, I'm sure that Arc graphics would be capable of real time playback powered by the GPU.

    Leave a comment:


  • coder
    replied
    Originally posted by sophisticles View Post
    I never noticed before, but SMPlayer apparently does not support hardware decode on Intel hardware, there is no option to enable it and the same holds true for the appimage version; hardware decode is available for NVIDIA hardware.
    Thanks for the info.

    Originally posted by sophisticles View Post
    ​I decided to try the GLIBC version of AviDemux Appimage, which normally decodes via CPU but has the option to decode using LIBVA when using Intel graphics.
    I really like AviDemux. It has builtin support for keyframe-only editing, which I've used to edit MPEG2-TS files without transcoding. That said, I really haven't gone very deep into its capabilities, so I can't say how it compares as a NLE, overall.

    Originally posted by sophisticles View Post
    ​​Edit: I just tried with a 6k ProRes file, GPU decode does work when using SMPlayer.
    On what, a Nvidia GPU? Which one and how fast was it?

    Leave a comment:


  • sophisticles
    replied
    Originally posted by coder View Post
    My guess is that the build you're using probably doesn't have support for Intel's hardware decoder compiled-in. Either that, or you need to play with the options so that it gets used.

    How did you get SMPlayer on your system and what distro are you using?
    I got SMPlayer through the official Manjaro repos, using Manjaro Cinnamon .

    I never noticed before, but SMPlayer apparently does not support hardware decode on Intel hardware, there is no option to enable it and the same holds true for the appimage version; hardware decode is available for NVIDIA hardware.

    I decided to try the GLIBC version of AviDemux Appimage, which normally decodes via CPU but has the option to decode using LIBVA when using Intel graphics.

    Repeated the earlier tests using the built in player, hardware decode does work for AVC, HEVC, VP9 only.

    Here's the thing, considering how many more formats are supported for decode via GPU with Intel, and considering that a faster GPU would yield faster decode performance, I have to conclude that NLE developers would do well to support GPU powered decode instead of hardware decode.

    Edit: I just tried with a 6k ProRes file, GPU decode does work when using SMPlayer.
    Last edited by sophisticles; 01 December 2024, 07:14 PM.

    Leave a comment:


  • finalzone
    replied
    Originally posted by Espionage724 View Post
    Looked cool and I wanted to try it around when Fedora 41 came out, but Resources only officially releases as a Flatpak.
    An unofficial version is available through Atim COPR which just landed version 1.7.0 for Fedora 41.
    Last edited by finalzone; 01 December 2024, 02:32 PM. Reason: Updated info

    Leave a comment:


  • nokyan
    replied
    Originally posted by peterdk View Post

    Hi, you're the dev right? Thanks for this awesome app! Wondering why indeed it does not show these speeds? Almost no app has that while it's quite useful? I need to lspci -vv for it and then mentally decode the data there.

    In case it's not a don't want it, I might consider trying to add that, since I dabble in some Rust besides my daily mobile dev job.
    Yes, I'm the dev, thank you for your kind words.

    I haven't implemented showing PCIe link speeds because I try to keep a balance between useful things to show and not overloading the UI with every possible thing to show. I personally found PCIe link speeds not super useful (especially since they usually don't change, I believe), but if there's demand for that, sure, why not. If you could open an issue for that on GitHub (or open a PR if you want to give it a try yourself), that'd be great.

    Leave a comment:


  • peterdk
    replied
    Originally posted by nokyan View Post

    Resources does not display PCIe lanes nor link speed.
    Hi, you're the dev right? Thanks for this awesome app! Wondering why indeed it does not show these speeds? Almost no app has that while it's quite useful? I need to lspci -vv for it and then mentally decode the data there.

    In case it's not a don't want it, I might consider trying to add that, since I dabble in some Rust besides my daily mobile dev job.

    Leave a comment:


  • Stebs
    replied
    Didn't knew this one, and on first glance, I must say wow, well done. On AMD, GPU Encoding and Decoding are even shown separate...

    Even while being on KDE, I'm gone try this out for some time instead of Mission Center. That one was also nice but sometimes missed processes with high loads (in doubt, htop is always the answer).

    What do I miss? hmm, perhaps showing the corresponding values while mouseover a graph - but that is probably using a lot of resources?

    Leave a comment:


  • reba
    replied
    Originally posted by QwertyChouskie View Post
    I prefer Mission Center personally, I like the layout better and it also can manage services. Both are solid options though, much better than GSM.
    Just tried it out of cusiosity and because they, at least, provide an AppImage.

    - But the interface feels sooooo sluggish
    - The animations just get in my way of seeing the information, scrolling is a pain and slow
    - Mouse cursor is enlarged and not correct
    - Window icons are broken
    - It wakes up the dGPU vom D3cold just to show there is nothing using it (you serious?! Check power state before doing stupid crap)
    - Not much information presented, especially on the running tasks page
    - Overall not much information or information that is irrelevant because trivial

    Leave a comment:

Working...
X