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.
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.