Currently, the total hertz is based on all the slaves in list, regardless of their state, and if they’re enabled/disabled. The used hertz is based on all the slaves that are idle or rendering.
So there are a couple of things we should do here:
Disabled slaves should not apply to the total or used values.
The used value should also be based on slaves that are currently starting jobs.
We don’t do any filtering of slaves that are on the same machine (Deadline doesn’t have a concept of primary vs secondary slaves). However, I believe we agreed on having idle slaves add their cpu usage to the utilization so that’s more accurate.
The problem with secondaries, is that they are mostly idle. So when the machine’s primary slave is rendering at 100% cpu usage, the idle secondary would also reflect that? If yes, i think that would basically result in the same values as “not counting primary/secondary twice” would. Is that already in deadline7?