How to format (partition) an SSD hard drive?

Question

Solid State Drives

You need to split (make markup) the SSD hard drive.
So relatives bought this SSD in their PC and they say help replace the HDD.
They use Win10 64x. I have already read theories about optimizing Windows.
But I did not understand how to do the markup.
So I installed Win10 on a clean SDD. Win means made an automatic breakdown of the hard drive in GBT format.
Everywhere on the Internet it is written that for durable work you need to have 15% free space for even memory wear.
So I sit and think, my relatives will easily beat him to the very "tomatoes" :), and there will not be a byte of free space left. To do this, I moved the desktop, documents, music, downloads, and other personal data to D:.
But how to protect the screw from overflow?
Problems:
-Restore points,
-Caching.
-Archiving.
For example, drive C: is 95%(90%) full (assuming drive D: is 100% full, of course).
(I set it up so that the user can fill D: by 100%, i.e. movies saved to the desktop, which is located on D: And at the same time the PC was still fast).
But I have not dealt with SSD yet. so I think that Windows will not delete the restore point at C: 95%, D: 100%?
I think that with 95% (90%) overflow of windows, the rest of the place will be stupidly used for caching, restoring and archiving.
.
How to split an SSD so that when the logical disks are full, the SSD does not wear out?
Is it possible to not partition 15% of logical disks in an SSD?
Is it possible to not mark up 15% in GBT markup in SSD, since GBT markup is a container for MBR markup?
How does the SSD understand that this space is not being used? (after all, any deletion is a deletion of a reference in memory)
The SSD controller itself climbs into the GBT markup and analyzes what is free and what is not ?, or does Windows give it commands what to read data and what is emptiness?
Does the SSD controller in GBT markup recognize an unallocated area, provided that Windows gives commands that there is data and that there is a void in the logical drives?

Answer 1

I have already read theories about optimizing Windows.

And what to read there - I bought it, stuck it instead of HDD, that's all.
It is also advisable to check that the disks are included in AHCI, but this is not a recommendation for SSDs, but in general for all disks.
There is absolutely no need to optimize the OS.
There is also no special point in doing any special breakdown for home use in your case.

Everywhere on the Internet it is written that for durable work you need to have 15% free space for even memory wear.

The fig is written. You need free space, without it your recording speed will drop. And it has virtually no effect on wear.

I think that Windows will not delete the restore point at C: 95%, D: 100%?

Recovery points are deleted when their size exceeds the limit, or when they interfere with writing data to disk.
If the disk is full, restore points will be deleted.

How to split an SSD so that when the logical disks are full, the SSD does not wear out?

So that the SSD does not wear out, the breakdown will not help, wear can only be reduced by completely refusing to use it and storing it in a dry and cool place.

Is it possible to not partition 15% of logical disks in an SSD?

It is possible, and in some cases even necessary, for example, when TRIM does not work or when there is a large write load on the disk, this is called over provisioning. Just make sure that the unallocated space is cleared of data, otherwise there will be no sense from this.

Is it possible to not mark up 15% in GBT markup in SSD, since GBT markup is a container for MBR markup?

I have not heard about GBT markup - what kind of beast is this? If we are talking about GPT - then what does it have to do with containers and MBR? Just another layout option, more progressive and less restrictive than MBR.

How does the SSD understand that this space is not being used?

Doesn't understand at all.
There is a write or read from the LBA address - it means it is used, if not, it means it is not used.

The SSD controller itself climbs into the GBT markup

I don’t know what GBT is, but the controller doesn’t go anywhere, and doesn’t know what kind of file system you have there, doesn’t know if you have a file system, whether you formatted the disk or not - all this is unknown to him. The controller simply writes the data that is given to it for writing, and reads the data that was requested for reading, and along the way is engaged in internal optimization, which happens outside the disk does not concern it.
The main difference between HDD and SSD in this regard is that the
HDD writes information to where it was told where the file system defined the data.
SSD writes information wherever it sees fit. And it always uses the entire disk capacity for writing!
But neither the HDD nor the SSD knows anything about how you marked them and what file system you placed on them.

Answer 2

The SSD controller and Windows 10 have enough brains to solve these problems without your participation.
% for wear is already included in the drive itself. Just create a partition the size of the disk itself and spend your time on something more useful.