It's astounding the amount of CPU that things use doing nothing. Zoom takes constant 4% CPU usage to show a login screen and Slack does 20% doing nothing. Turning off gifs for Slack drops that back down to ~5%. But still 5% for a chat app at idle.
To be clear, it’s not apple’s fault —- but they do own the OS and the scheduler.
I’ve previously experimented with the kill command, stopping and starting applications. Apple could do this automatically and reduce that 5% to 1%, or even 0.1%.
This assumes that Slack is doing something over and over many times, rather that just being super-slow at doing the thing once.
Slack is a chat app, and as you say has no business requiring 5% of a CPU. If it’s doing that because it checks for new messages more often than once per second, Apple can help them with that. If they actually require more than a second to check for messages, then their requirements or their developers need to change.
