Re:Apple's APFS Migration: A Feat of Engineering
by KRAKRISMOTT on Monday April 15, 2024 @03:10PM
(#40044520)
They ought to compensate users for the excessive flash memory writes if the users are going to be guinea pigs for their beta test.
[ Parent
| on HN ]
Re:Apple's APFS Migration: A Feat of Engineering
by axoltl on Monday April 15, 2024 @03:12PM
(#40044541)
The writes would go to /dev/null. No "excessive flash memory writes" were done, as they were testing the ingest portion.
Re:Apple's APFS Migration: A Feat of Engineering
by orf on Monday April 15, 2024 @03:27PM
(#40044688)
Why?
Re:Apple's APFS Migration: A Feat of Engineering
by KRAKRISMOTT on Tuesday April 16, 2024 @02:20AM
(#40048895)
Because flash memory has a limited number of write cycles and an entire file system migration will gobble up a good chunk of it.
Re:Apple's APFS Migration: A Feat of Engineering
by orf on Tuesday April 16, 2024 @03:29AM
(#40049262)
Yes, but why should users be compensated for that.
And why would it use a large portion of that, rather than an additional 1 write per cell?
Re:Apple's APFS Migration: A Feat of Engineering
by KRAKRISMOTT on Tuesday April 16, 2024 @04:30PM
(#40056781)
Because if you see OP's comment, they were testing their migrator on real users' devices (in what I presume is a blue green manner, without explicitly informing them except in small print) before their "official launch". If their beta test didn't go well, they will have to rollback their change, consuming more writes.