5 ms·
AFAIK this problem seems to have gone away with the M1 based Macs. Can anyone confirm?
by als0 4y ago
AFAIK this problem seems to have gone away with the M1 based Macs. Can anyone confirm?
- smoldesu 4y 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 4y 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 4y 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.