![]() ![]() OP includes the built-in amount the manufacturer has hidden from the user, plus the unallocated amount (the space the user has hidden from the OS), plus free space within partitions (as marked by TRIM). I think many, if not most, manufacturers also have some built-in OP, so determining the amount of OP is not always clear. I might still leave some space unallocated, but maybe not as much. With multiple partitions you'll almost never be 100% full on all of them at the same time, so there should always be free space somewhere to contribute to the OP pool. If you have multiple partitions, it becomes less clear cut. After all, if you put it in a partition and swear not to use it, then why bother? Just leave it unallocated. Personally, my feeling is that if you have a single partition, you may as well leave space unallocated. ![]() Or both could be completely full if you've left 20% unallocated. So one partition could be completely full if another has lots of room. If you have multiple partitions, you need to aggregate the free space on all partitions. If you instead have a single partition occupying only 80% of the SSD capacity, you can fill the partition to 100% full. If you have a single partition occupying 100% of SSD capacity, you're okay if you never fill the partition to more than 80% full. Let's use an example of 20% overprovisioning (OP). (The purpose of TRIM is to tell the SSD what space within partitions is truly free and available for garbage-collection.) It works at the drive level, not the partition level, so "unused space" includes unallocated (unpartitioned) space plus free space within all partitions. To work effectively, garbage-collection needs unused space on the drive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |