In other words, writing to an empty block is fairly quick, but writing to a partially-filled block involves reading the partially-filled block, modifying its value, and then writing it back. This will need to happen with every block the file must be written to. When you go to write a file, it will have to read the partially filled block into its cache, modify the partially-filled block with the new data, and then write it back to the hard drive. When an SSD has little free space, it has a lot of partially filled blocks. Solid-state drives are actually designed to spread data around the drive evenly, which helps to spread out the wear effect - rather than one area of the drive seeing all the writes and getting worn down, the data and write operations are spread over the drive. The drive can simply read the data from whatever sectors it resides in. On a solid-state drive, there's no mechanical movement. If a file's data is spread out over the drive, the head will have to move around to read all the little pieces of the file, and this will take longer than reading the data from a single location on the drive. On a mechanical hard drive, defragmenting is beneficial because the drive's head has to move over the magnetic platter to read the data. ![]() What's more, you won't see any speed improvements from defragmenting. ![]() The storage sectors on an SSD have a limited number of writes - often fewer writes on cheaper drives - and defragmenting will result in many more writes as your defragmenter moves files around. You shouldn't defragment solid-state drives.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |