Quote Originally Posted by Ao1 View Post
So in this instance the OS issued a single command to the SSD to wipe ~ 1.5 gigabytes of “deleted” data? I assume the SSD controller then waits for a quiet period and then deletes the data when it will have no/ less impact.
Yes, and that is certainly one way that the SSD controller could handle the "backend" processing of the TRIM commands from the OS.

By "backend", I mean the actual manner in which (and when) the SSD controller performs various flash management tasks (e.g., wear-leveling) based upon the DSRs that it has received from the OS.

As you know, essentially the TRIM commands currently provide a way for the OS to notify the SSD that a specific set of (logical) blocks/sectors upon the SSD are considered by the file system to be "deleted data blocks" (that is, sectors upon the SSD that the file system considers to no longer contain valid data).

But as to what exactly the SSD does with these "trimmed" blocks/sectors (and when), this is, I believe, basically "vendor-specific" at the current time.