3 ms·
MacOS' indexer is equally as bad. The amount of time's I've seen 10 mdworker threads pinning my CPU is staggering...
by smoldesu 5y ago
MacOS' indexer is equally as bad. The amount of time's I've seen 10 mdworker threads pinning my CPU is staggering...
- als0 5y agoAFAIK this problem seems to have gone away with the M1 based Macs. Can anyone confirm?
- smoldesu 5y agoI'd imagine it's not an issue since Grand Central Dispatch will only assign it to a single core cluster, which leaves the other cores free to do their own processing.
- ceeplusplus 5y agoI believe indexing tasks only run on e-cores, at least from quick glances at Activity Monitor. I also see more kernel code run on e-cores when I'm compiling code, not sure if Apple is moving blocking syscalls onto e-cores and swapping threads or something (intuition tells me this shouldn't lead to perf gains due to context switch cost, but who knows).
- MBCook 5y agoI’ve been led to believe that all non-interactive tasks only run on the efficiency cores by default. Of course code can request alternate priorities. It’s entirely possible that Apple has written things like the spotlight indexer to explicitly make sure they run that way as well, or it may just be an intentional result of the policy.
- astrange 5y agoSpotlight runs at a low CPU priority, so it doesn’t use a lot of power (theoretically) and on Intel won’t increase P-states. The CPU % doesn’t mean much at all except it’s runnable.
- smoldesu 5y agoIn practice my CPU hits ~80c and makes the system nearly unusable. I just disabled Spotlight indexing altogether.
- sliken 5y agoTo be fair backups are one of many things (like compiling, video conferencing, or even just looking at the laptop wrong) that makes x86-64 macs run their fans run out. My particular case is an i9 in a mbp 16". It throttles heavily while making impressive noise any just about any light workload that's not pure idle.