Look at the raw values for E9/F1/F2 instead of the normalised values.
They are currently expressed in hexidecimal, but can be changed to decimal numbers using the menu:
Function -> Advanced Feature -> Raw Values -> 10 [DEC]
Don’t select one of the “10 [DEC] - 2 byte” or “10 [DEC] - 2 byte” functions.
Then the raw values will be a little more understandable for mortals.
Looking at your values, Drive 1 is running at about 1.28 write amplification, thus would reach End of Specification life (given similar workload for the rest of its long long life) at about 256,000 GiB Written. Given a similar workload to it’s current workload, That will be at 520 thousand hours, or 60 years of age (something else will definitely happen before then … probably)
Drive 2 is running a bit worse amplification, (but less written over time), so at it’s 1.41 write amplification, thus would reach End of Specification life at about 234,000 GiB Written. That makes it about 565 thousand hours (less written on this drive, so longer life), or 66 years of age.
Of course, this needs to be taken with a reasonable sized grain of salt, as I have no idea how the controller or NAND will handle decades of life … in all likelyhood it probably won’t. But yeah, you really have nothing to worry about in terms of NAND wear.
Good Programs to do SSD benching are Cystaldiskmark, as ssd, and ATTO.
Just a suggestion of just how far a Sandisk Extreme 120gig drive may go past it’s specification life:
After 95 days of constant write load, this drive has endured 721,201 GB of NAND writes, which is more then twice the specification life of the NAND. The 4 reallocations happened very early in the drive’s life (first for TiB written). Drive is still going as fast as did when it was originally started, about 125meg per second write average, with 145meg per sec during the write cycle.
