fzabkar wrote:
I didn't forget anything, I just ignored it because the firmware and OS are optimised so that it makes essentially no difference to the calculation these days.
I wouldn't call it "optimized" it's just the way it works. FS driver operates in clusters, so when you work with files, even if you change one byte - the whole cluster will be updated, except for a file record that can be smaller than data cluster in size
On a side of SSD it depends greatly on firmware. There were SSDs that split data by byte between two pages, so when you want to write one byte of data (from user perspective) and a data cluster (from FS driver perspective) at least two pages will be updated on that particular SSD, because data will be split evenly between two pages, that's just a real life example, all SSDs are different inside
There are some SSDs that report number of erase cycles for the whole drive: essentially it represents number of erase cycles on all data cells (it is possible to calculate this value because of wear leveling mechanism)
Some SSDs even show % of life left based on that erase cycles number and theoretical SSD usage per day
End user can rely on those values and even try to calculate SSD's "life expectancy" based on Power On hours and erase cycles