The information In hard drives it is stored sequentially. This is because, as it is carved on a magnetic plate that rotates at high speed. And it's a head recorder. This should follow the rotation of the plate in question.
The container, on the other hand, is separated categories. Each field is part of the surface of a hard disk, where data can be recorded. A collection of several interrelated fields form what is known as «Collection» (of course, a group).
There the drive head You have to record a piece of information, the first thing you do is to find the first free field at the top of the plate. But it doesn't matter how big that file is. Therefore, when our hard drive is new and has no data recorded in it, the disk header can record the data in sequence without any problems. The problem occurs when we use a disk for a while.
Breaching a hard drive automatically organizes all data
As we use our hard drive, the surface of it is full «Holes» for details. This happened as we erased the data we recorded. This information leaves spaces where no data is stored. So, when the hard drive will save a new piece of information, the first thing they will do is fill the empty holes in the plate. The problem now is that new data they do not have to have the same volume as the previous one. With it, Windows will store information in different fields.
This, in turn, triggers that information episode That is, the data is not close to each other. The result of this fact is that access to data will be much slower if the data is isolated from each other. As the hard disk head must jump between different disk positions to read the stored data in the fields.
In the image you can see that, the blue fields contain information that has not yet been separated. However, red has separate information.
Opposition The hard disk copies the partitioned data of the hard disk partition, so that they all fit together. To copy them again so they can be edited in sequence, side by side.
Is it necessary to perform the same process with our SSD?
No. Not only is it not necessary to perform the undo process on SSD But it can also hurt.
Since SSDs do not have turntables such as hard drives, details are stored on memory cells in a sequential way. Also, not with head movements recording or reading data, they do not have to be close. However, on the other hand, each NAND Flash memory cell has a limited number of write cycles.
This number is significantly lower than the cycles supported by the hard disk. Therefore, it doesn't make sense to debug SSD. Otherwise, doing so does not deserve any benefit to work when accessing data.
