> My main point is that a global CPU graph helps you identify acute CPU consumption as it happens which is the main mechanism that helps me identify things like

> My main point is that a global CPU graph helps you identify acute CPU consumption as it happens which is the main mechanism that helps me identify things like Spotify getting stuck in a spinlock or a browser tab devouring my battery. Seeing "Google Chrome" show up in Activity Monitor's energy chart when you check it periodically isn't as helpful. If you want to know 'what is using all by battery' after a couple hours using it, you want to know the average power usage by app, which activity monitor gives you. Battery life is the point of this thread, not random lock ups. > Good point about iStat Menus consuming its own resources. It has two processes afaict with its main process staying below 1% CPU. I wish we could just get rid of 'cpu %' as a metric on modern machines, or at least scale it based on P-state. Saying process X is taking Y% of the CPU is pointless if you don't also communicate the P-state, and chances are you don't even know which core the process is running. Point is, I'm sitting here almost completely idle and there are plenty of tasks 'using 3-5% of my CPU', of course the CPU is running at 800MHz no where near it's all core peak of 2.7Ghz, much less it's single core peak of 4.5Ghz. What does 1% CPU even mean in this world?