4 ms·
That's really strange. Why would encryption affect APFS so badly but not HFS+?
by mikeash 9y ago
That's really strange. Why would encryption affect APFS so badly but not HFS+?
- convivialdingo 9y agoLots of reasons. If crypto is part of the syscall path, then you definitely pay with latency. If you can push IO to a worker thread then you can release the user call faster. This also requires tuning the read-ahead cache more aggressively. It could also be a change in crypto algorithm, unaligned page IO, or any other overlooked IO latency problems.
- j45 9y agoAt a high level, I believe APFS encrypts files individually (and uniquely) instead of the whole drive. Have to do some more reading :)
- Someone 9y agoNot instead of, but optionally in addition to (https://developer.apple.com/library/content/documentation/FileManagement/Conceptual/APFS_Guide/Features/Features.html https://developer.apple.com/library/content/documentation/Fi...) On Mac OS, it seems you only get full disk encryption, though (https://arstechnica.com/gadgets/2017/09/macos-10-13-high-sierra-the-ars-technica-review/6/ https://arstechnica.com/gadgets/2017/09/macos-10-13-high-sie...)
- j45 9y agoAppreciate the clarification. Both are better than just one.