medianalysisd for example, which frequently pummels 1-2 cores of my machine for long stretches of time, runs local on-device models to analyze the media on your machine.
You know, that brings something to mind that I haven't seen mentioned (so far). If you wiped the machine, it has to rebuild all that "knowledge". Apple announced that they'd rebuild the Spotlight index with an update to 26 so that people upgrading to 27 could use the new AI features immediately. Maybe the timing rules this out, but keep in mind that the device could be running processes that will eventually expire / run only on new content. Could that be a factor?
I know a new phone or Mac bangs hard on indexing even pre-foundation models. I haven't set up a new device with 27, so I don't know how much that might have increased.
I wiped the machine weeks ago, not recently, and I wiped it while debugging the issue, which existed prior to wiping it. I was having these issues on Tahoe on my M5 (came with it, unfortunately), but not Sequoia on my M2 (occasionally things would spike but it always ran cool when idling or doing my normal work). The issues got even worse on Golden Gate. Upgraded my M2 to test and it started exhibiting the same problems.
I also have as much indexing turned off on Spotlight as I can, and that is another issue. Spotlight seems to disrespect my settings and indexes/displays more than it should. Seems like an open, unaddressed bug. I've assumed this is related to the Spotlight-specific CPU usage issues I have but it doesn't explain the others.
medianalysisd for example, which frequently pummels 1-2 cores of my machine for long stretches of time, runs local on-device models to analyze the media on your machine.
You know, that brings something to mind that I haven't seen mentioned (so far). If you wiped the machine, it has to rebuild all that "knowledge". Apple announced that they'd rebuild the Spotlight index with an update to 26 so that people upgrading to 27 could use the new AI features immediately. Maybe the timing rules this out, but keep in mind that the device could be running processes that will eventually expire / run only on new content. Could that be a factor?
I know a new phone or Mac bangs hard on indexing even pre-foundation models. I haven't set up a new device with 27, so I don't know how much that might have increased.
I wiped the machine weeks ago, not recently, and I wiped it while debugging the issue, which existed prior to wiping it. I was having these issues on Tahoe on my M5 (came with it, unfortunately), but not Sequoia on my M2 (occasionally things would spike but it always ran cool when idling or doing my normal work). The issues got even worse on Golden Gate. Upgraded my M2 to test and it started exhibiting the same problems.
I also have as much indexing turned off on Spotlight as I can, and that is another issue. Spotlight seems to disrespect my settings and indexes/displays more than it should. Seems like an open, unaddressed bug. I've assumed this is related to the Spotlight-specific CPU usage issues I have but it doesn't explain the others.