Each additional Safari window increases WindowServer’s memory use by 1.7 MB on an Intel Mac, but 50 MB on an M1 Mac – thirty times more.
Apple silicon
When running some tasks confined to E cores, the original M1 chip from 2020 completes them significantly quicker than an on an M1 Pro. Here’s the detail.
Users and other processes have very limited control over which threads are run on which type of core. As Apple Silicon develops, this is an area set for change.
For the great majority of Mac users, M1 series Macs are a big step forward. But some users want the impossible. What can’t M1 Macs do?
Fixes a bug which could incorrectly report the SSV was disabled on M1 Macs, and improves reporting of M1 Platform Security on non-English systems.
From the anatomy of the CPU cores, to the queues of threads in GCD, and assignment to a core cluster, this details how threads are managed for the M1 series chips.
Why can’t the taskpolicy command tool be used to promote software to be able to run on the M1 chip’s Performance cores? Does it change QoS?
How to discover what’s stored in your Mac’s NVRAM, how to reset it in Intel Macs, and how you can changes its variables.
Is it overhead from sandboxing, the file system, the throttling of I/O, or the limitations of the Efficiency cores? Is there anything a user can do?
Maybe you’ve just forgotten the password, or perhaps the owner/user of the Mac is no longer able to enter it. How to restore access to different models.
