Thu Dec 19, 2019 11:41 am
Sounds like marketing BS to me. A defrag tool running on the host does not have any knowledge of (or control over) the wear leveling or block allocation algorithms being used internally by the SSD firmware, other than what is exposed via the TRIM logic.
It can certainly make some educated guesses about the flash page size, and try to consolidate files into as few logical pages as possible, on the assumption that this will in turn map to the fewest possible number of distinct physical pages. But this is really no different than making sure the blocks in a file are stored contiguously and sequentially, which is what a defragger is supposed to do anyway.
Kind of reminds me of how back in the late '80s and early '90s, ads for headphones all had to tout that they were "digital-ready", even though that was completely irrelevant since the connection was still analog. Or how monitors had stickers on them that said "Windows Vista Ready" when Windows Vista came out. Uhh... if you just correctly implement the basic functionality everyone would expect from a product of this type, it'll automatically do this thing you're promoting as if it is some sort of revolutionary new feature...
Nostalgia isn't what it used to be.