Crucial v4 (256GB) Review
Performance Over Time & TRIM
I first ran HD Tach on a secure erased drive to get the baseline:
Next I filled the drive with sequential data and tortured it with compressible 4KB random writes (LBA space 100%, QD=32) for 20 minutes:
The result is rather interesting. Performance does not degrade significantly and after around 30% of the LBAs have been written to, performance is back to where it was after secure erasing.
As 20 minutes wasn't enough, I extended the length of the torture to 60 minutes:
And the graph is almost the same as after 20 minutes of torturing. The v4 seems to be doing active garbage collection, which means it tries to clean some blocks every time a write request comes in. As you can see, performance is getting better and better as the drive receives write requests and it's again back to brand new state after ~75GB of writes.
FInally I TRIMed the drive:
There are a few odd drops but overall write speed is what it should be. The drops are most likely related to internal task scheduling. A sent TRIM command does not mean that the drive will automatically exceute it as the controller may prioritize some other task, which leads to a scenario where all blocks are not cleaned.
Originally published at https://www.anandtech.com/show/6325/crucial-v4-256gb-review (Wayback Machine).



