In the old one (deadline7) our total was about 4x as big btw, so maybe its the total count thats not correct?
After restarting the monitor, i now get 44% of 93.7Thz. Weird.
Strange. We did make some tweaks to how we pull this info in 8.0, but if anything it should be more consistent (we’re always pulling the Max clock rate now, and caching it once at slave startup). Had a chunk of the Slaves just started up? I wonder if this is that WMI bug manifesting itself in a different way… We might return -1 or 0 until the value is successfully queried, which could explain that number being much lower before getting to the correct number.
Yeah, this was during the process of moving machines from deadline7 to deadline8. So this monitor was observing the migration basically.