That doesn't imply it should be slow; that should imply it should be fast. At least, given that macOS is using a copy-on-write filesystem such that you can sha

That doesn't imply it should be slow; that should imply it should be fast. At least, given that macOS is using a copy-on-write filesystem such that you can share blocks between multiple volumes/snapshots — which it is; and that the OS base-image is a sealed "everyone has the same cryptographic checksum" volume — which it is; and that Apple are using a binary-diff-based "create aside" OS-image update process, like ChromiumOS/CoreOS — which they are. They should only have to write out disk pages for the changes, and then just link the existing pages in to form the rest of the extents. Like a `btrfs receive`. But for some reason, despite all that fancy tech, it's still slow; and the install process still requires rebooting into a separate Recovery OS to do parts of the installation. Which, given the "create aside" part especially, is just ridiculous. You should be able to just run the installer in the background as you're using your device, and eventually be told "when you reboot, it'll be into the new OS."