Those timings are at the NAND level. If a block is not clean, i.e. it contains a small of amount of valid data, that data has to be relocated before the block is erased, which adds time to the operation. Deciding where the data ends up is a processing task, which takes time to calculate. What I tried to say was that when a drive is in a fresh state it doesn't have to worry about any of that.
A secure erase can be executed in under ~ 2 seconds, so there must be a way to access and erase all blocks more or less simultaneously, so a block erase can be very fast if the controller does not have to be concerned about checking to see if data is valid, mapping data or managing WA.
When the drive is in a used state processing time is required, which adds overhead. As can be seen below that overhead can vary significantly depending on the state of the drive.
![]()
Bookmarks