@ins0mniak @amerika @j @pwm @Suzu @f0x @phnt @sicp @tsubo @p @ceooffuggy @mrsaturday @romin @subnetter @sun @hakui it's getting worse though. the new GUI is so ugly I'm probably going to stop using my mac entirely except as a local LLM server (it has the 64gb unified V/RAM). that's in addition to having many many inscrutable daemons that phone home constantly, constantly use a fraction of the CPU with no obvious reason and whose function isn't immediately obvious without researching. And it's nearly impossible to get an answer for *why* any particular thing is happening because system logs seem to deliberately fight you when you look into it. Sometimes something will just pin multiple CPUs, and it's impossible to figure out why-- if the service in question is even emitting logs, often they'll be flooded with completely irrelevant details nobody would ever need to know, internal API operations, messages passed between stuff in kernel space that seem intentionally designed to make it hard to figure out what they're actually doing.

it's like a gish gallop that's meant to make you conclude "oh, OK I guess this is too complex for my tiny user brain I better go and just sit over here and accept whatever tim apple wants to give me!"

I never have this problem on linux. If a linux process is pinning a CPU, the logs almost always give hints as to why.