3 ms·
Yet at the same time it doesn't feel like it's doing any work. It's an M1 Pro but I still don't hear the fans kick in or feel it warming up at all. So I feel li
by c7DJTLrn 5y ago
Yet at the same time it doesn't feel like it's doing any work. It's an M1 Pro but I still don't hear the fans kick in or feel it warming up at all. So I feel like there is probably room for optimisation, whatever the update process does.
- ksec 5y agoThat is just M1, it sure eat up all CPU when doing it on x86.
- jeffbee 5y agomacOS schedules software updates on the "efficiency" cores of the M1, which is why it takes forever and doesn't seem to cause any slowdown.
- c7DJTLrn 5y agoThanks for the info. Wow, any idea why? How do you know this?
- jeffbee 5y agoI noticed it in Activity Monitor one day, then I looked at the docs and it’s a documented behavior.
- booi 5y agoThat’s actually pretty amazing. But sometimes I’ve set aside time to do the update and I’d like it to go as fast as possible. I wonder if there’s a way to force it on the performance cores?
- jeffbee 5y agoYes, I agree entirely. Once I wasted a half work-day waiting for Xcode to install itself, which is how I came to discover and research this feature. I would have much rather used my four fastest-you-can-buy cores than waste a morning waiting.
- rbanffy 5y agoIt should probably use all cores while there is an Apple logo and a progress bar (and the user is essentially locked out). Fun detail - newer IBM mainframes enable all cores (including the ones that are there but you didn't pay for) during the boot process to reduce downtime.