That would be called under-provisioning.
I haven’t read anything about how an SSD deals with partitions, so I don’t know for sure.
Since the controller intercepts the calls for specific locations, I’m inclined to believe that the controller does not care about the concept of partitions and does not segregate any chips, thus it would spread all writes across all of the chips.
Hello, good job showing your knowledge with a bunch of extraneous details.
Now, to increase your intelligence, see if you can boil your knowledge into a simplified explanation when that is what the question calls for.
An analogy is writing everything on one piece of paper with a pencil. When you need to change or remove something, you cross it out, instead of erasing, and write the new data to a clean part of the paper. When there are no more clean areas, you use the eraser to erase a crossed off section.
The larger the paper, the less frequent you come back to the same area again with the eraser.
Using an eraser on paper slowly degrades the paper until that section tears and never gets used again.
In general and simplifying, my understanding is:
There is the area where data is written, and there is the File Allocation Table that keeps track of where files are placed.
When part of a file needs to be overwritten (either because it inserted or there is new data) the data is really written to a new area and the old data is left as is. The File Allocation Table is updated to point to the new area.
Eventually, as the disk gets used, that new area eventually comes back to a space that was previously written to, but is not being used. And that data gets physically overwritten.
Each time a spot is physically overwritten, it very very slightly degrades.
With a larger disk, it takes longer to come back to a spot that has already been written to.
Oversimplifying, previously written data that is no longer part of a file is effectively lost, in the way that shredding a paper effectively loses whatever is written, and in a more secure way than as happens in a spinning disk.
With spinning disks, I preferred Seagate over Western Digital. And then move to HGST.
Back in those days, Western Digital had the best warranty. And I used it on every Western Digital. But that was still several days without a drive, and I still needed a backup drive.
So it was better to buy two drives at 1.3 x the price of one Western Digital. And then I realized that none of the Seagate or HGST drives failed on me.
For SATA SSDs, I just get a 1TB to maximize the cache and wear leveling, and pick a brand where the name can be pronounced.
For NVME, for a work performance drive, I pick a 2TB drive with the best write cache and sustainable write speed at second tier pricing.
For a general NVME drive, I pick at least a 1 TB from anyone who has been around long enough to have reviews written about them.
Some of the best and worst decisions people have made started with, “I was bored.” Ha!
From the drives I have seen, usually there are 3 write-cache sizes.
Usually the smallest write-cache is for drives 128GB or smaller. Sometimes the 256GB is also here.
Usually the middle size write-cache is for 512GB and sometimes 256GB drives.
Usually the largest write-cache is only in 1TB and bigger drives.
Performance-wise for writes, you want the biggest write cache, so you want at least a 1TB drive.
For the best wear leveling, you want the drive as big as you can afford, while also looking at the makeup of the memory chips. In order of longest lasting listed first: Single Level, Multi Level, Triple Level, Quad Level.