Comment by quotemstr
17 hours ago
For decades now, we've had to deal with articles like this one. People who know just enough to sound credible mislead those who known even less into mutilating their systems in the name of "optimization". This genre is a menace.
Much harm has arisen out of the superstitious fear of 100% CPU use. Why wouldn't you want a compute bound task to use all available compute? It'll finish faster that way. We keep the system responsive with priorities and interactivity-aware thresholds, not by making a scary-looking but innocuous number go down in an ultimately counterproductive way.
The article's naive treatment of memory is also telling. The "Memory" column in the task manager is RSS. It counts shared memory multiple times, once for each process. You literally can't say the 5MB "adds up". It quite literally is not amenable to the arithmetic operation of addition in a way that produces a physically meaningful result. It is absolute nonsense, and when you make optimization decisions based on garbage input, you produce garbage output.
It's hard to blame Apple for locking down the OS core like this. People try to "optimize" Windows all the time by disabling load-bearing services that cost almost nothing just so "number go down" and they get that fuzzy feeling they've optimized their computer. Then the rest of the world has to deal with bug reports in which some API mysteriously doesn't work because the user broke his own system but blames you anyway.
> Much harm has arisen out of the superstitious fear of 100% CPU use. Why wouldn't you want a compute bound task to use all available compute? It'll finish faster that way.
Because it hurts the speed/responsiveness of stuff you actually care about. It also has other negative side effects like fan noise and temperature, which with bad insulation in MacBook it can even physically burn. Pretty obvious stuff if you don't discard issues as superstitions
> It'll finish faster that way.
The usefulness of which might be none: some background maintenance process finishes in 5 seconds that I don't notice vs in 1 seconds while turning the fans on or making my app slower
> We keep the system responsive with priorities and interactivity-aware thresholds,
Only in your fantasy, in reality you fail at that, so "superstitions" arise
> It's hard to blame Apple for locking down the OS core like this.
Of course, if you ignore real issues with bloat, and only notice the mistakes, but that's a self-inflicted perspective
> by disabling load-bearing services
The article mentions that there is not even basic information on what services do, it's similar in Windows, so maybe the proper way out is teach people and also debloat the OS proactively to give them less of an incentive to do it themselves?
> The "Memory" column in the task manager is RSS. It counts shared memory multiple times, once for each process.
It’s “footprint” and no it does not do that
Perhaps it did a while ago. Now, https://www.bazhenov.me/posts/activity-monitor-anatomy/ is a good read. Thanks. It's much better than RSS, although I'm at still not sure that I like the inclusion of private compressed memory. In any case, thanks for the correction.
One of the ways both macOS and iOS get good battery life is burst-y CPU loads to return the CPU to idle as quickly as possible. They also both run background tasks like Spotlight on the e-cores whenever possible. So some process maxing out an e-core is using a lot less power than one maxing out a p-core. Background processes maxing out a core occasionally is not as much of a problem as a lot of people seem to assume.
You're not wrong. Let's hope that articles, like the OP's post, shed light on further optimizations that Apple is now fully in charge of making.
I see nothing in the post that convinces me Apple ought to change a single thing.