Earlier quoted context omitted.
Activity Monitor itself also consumes a lot of CPU. And you tend to only use it when you've already suspected a problem, like when your fans start running. What's nice about having a global CPU graph is that you get used to normal idling levels and will start to notice anomalies. You're also just closer to the pulse of your computer. What exactly are normal bandwidth consumption levels over the course of a day? What…
> Activity Monitor itself also consumes a lot of CPU. And you tend to only use it when you've already suspected a problem, like when your fans start running. MacOS always tracks the energy usage stats so you don't have to keep activity monitor open, just look at the 'Average Energy Impact' column. iStats menu also uses a fair bit of CPU, similar to Activity Monitor, it's just split into a couple processes so it doesn…
Good point about iStat Menus consuming its own resources. It has two processes afaict with its main process staying below 1% CPU. I bet that number sees an increase once you start turning on more HUDs like the temp/fan sensors and jacking up the update frequency though.