C
C
Clementino2021-03-23 10:28:47
Solid State Drives
Clementino, 2021-03-23 10:28:47

Does dividing ssd by log. sections of its service life?

I heard this version, the essence is something like this:
"It is bad to divide an SSD into logical partitions, because internal optimization works only within one logical disk.
Let's say if the disk is divided into 2 partitions, one OS is installed, then the partition with the system is overwritten more often, and ssd tries to write evenly across cells based on wear.And if, for example, a terabyte disk has only 100GB free (100GB system partition), and the rest is dead weight, then the tbw resource can be divided by 10. Instead of 150TB, you get a resource overwriting up to 15tb".

Is there any truth in this, is it worth leaving the ssd with one partition to increase its lifespan?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
Z
Zettabyte, 2021-03-23
@Clementino

if the disk is divided into 2 partitions, one OS is installed, then the partition with the system is overwritten more often

The SSD translation mechanism should not consider any partitions. The disk firmware does not know how you will use it, how you will share it, and how and what you will burn.
The OS wants to write to sector No. 322223 (which you have within the boundaries of the system partition), the disk will tell it that it has written, and it will write to "sector" No. 184639305, setting a correspondence between them in the translation table. When overwritten, the actual location of the data will change again.
if, for example, a terabyte disk has only 100GB free (100GB system partition), and the rest is dead weight, then the tbw resource can be divided

Yes, having little unallocated / unused volume of the entire SSD is bad. "Running" a small part of the disk is easier than its entire volume.
Manufacturers promise that even static data is "mixed" by the disk inside itself, regardless of the user, but you have no way to check how this works and whether it happens at all.
Some promise to actively move even frequently read data (apparently so that it is better read and does not require error correction by the controller), but here, too, you can only rely on promises.
Better try not to lower the amount of free space below 25%. The more modern the SSD model, the more important it is.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question