3 ms·
Honestly unless something seems to be sweating the box there's not a great reason to monitor it all the time. By far the biggest CPU/memory culprits are web pag
by noduerme 5y ago
Honestly unless something seems to be sweating the box there's not a great reason to monitor it all the time. By far the biggest CPU/memory culprits are web pages, but just looking at a bunch of chrome or ff processes doesn't really help determine which it is. Activity Monitor's own GUI is a pretty serious offender, running around trying to allocate icons and graphs for all those apps. If you just need to know what's going on, `top` on the command line will watch it for you. But usually (from a 2015 mac perspective) there's no need to keep an eye on it.