How much visibility do you get into power draw from various components with procpower? #6
Replies: 2 comments
-
|
Just for the log I sent Chris an email |
Beta Was this translation helpful? Give feedback.
-
|
Abridged answer from didi
Another snippet that might be useful:
My reading of this is that she probably would be in scope if they shared information about how much power they were using, but this is limited by the fact that many work like a black box so it's quite hard to see what's happening inside. This limits they utility for the modelling approach that ProcPower uses. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello there.
I have a question about what is feasible when using something like pro power to understand the power drawer of an operating system system using Linux.
I am aware that some of Apple's own energy usage monitoring tools where an influence on the ProcPower and related projects, and I use a macbook M1 myself. Here's what I see with a tool iStat Menus,in addition to the Energy tab in Activity Monitor:
I don't have a Linux machine handy right now I can run ProcPower on, so I'm not sure what is in scope in terms of being able to see power draw you can attribute to a process - would this cover GPUs as well as stuff like RAM and CPUs?
I can totally see how an external screen would be out of scope, but how much visibility do you otherwise get? I know about RAPL for example, but is there visibility into graphics cards or other connected tools?
Beta Was this translation helpful? Give feedback.
All reactions