NON-TRIM Environment Testing
In many ways, Corsair’s Performance 3 should thrive in an environment that doesn’t support TRIM. To recreate this, we first modified our testbed so that it would not pass on the necessary cleaning commands. Meanwhile, to artificially induce a degrade state we ran eight hours of IOMeter set to 100% random, 100% write, 4k chunks of data at a 64 queue depth across the entire drive’s capacity. At the end of this test, the IOMeter file is deleted and the drive was then tested. This will replicate drive performance after extended heavy usage prior to any self maintenance routines kicking in and is indicated by the “Dirty” results below.
In order to allow each drive’s self-maintenance routines to kick in, we then wait 30 minutes (Dirty + 30 results) with the system at idle and rerun the tests.
To help give as both a detailed and practical overall picture of a given drive’s ability in this severe environment we have chosen two tests: one synthetic and the other more real world in nature.
Synthetic Results
Since reads are usually not greatly affected by a degraded state, for our synthetic non-trim test, we have chosen our standard sequential write test. By opting for this test and not one of our other shorter tests, the controller will not be able to compensate for being in a degraded state by using over-provisioning, caching or other similar buffers to hide the true state of the drive. To put it simply, by writing data across the entire drive, we will quickly see how big an impact this environment will have on them.
Real World Results
For a real world application we have opted for our standard Vista load time test.
These results really do speak volumes about the amount of performance Corsair has wrung from the Marvell controller. Not only is this drive able to recover from a degraded state faster than anything else we have seen before but it was also able to successfully mask its degraded state quite well. This means an end user will never actually "feel" like their Performance Pro is running slower than when it was brand new, even after a year of heavy usage. The extra cache space really does pay dividends and the payout is one bloody impressive drive for non-Trim environments.
NON-TRIM Environment Testing
In many ways, Corsair’s Performance 3 should thrive in an environment that doesn’t support TRIM. To recreate this, we first modified our testbed so that it would not pass on the necessary cleaning commands. Meanwhile, to artificially induce a degrade state we ran eight hours of IOMeter set to 100% random, 100% write, 4k chunks of data at a 64 queue depth across the entire drive’s capacity. At the end of this test, the IOMeter file is deleted and the drive was then tested. This will replicate drive performance after extended heavy usage prior to any self maintenance routines kicking in and is indicated by the “Dirty” results below.
In order to allow each drive’s self-maintenance routines to kick in, we then wait 30 minutes (Dirty + 30 results) with the system at idle and rerun the tests.
To help give as both a detailed and practical overall picture of a given drive’s ability in this severe environment we have chosen two tests: one synthetic and the other more real world in nature.
Synthetic Results
Since reads are usually not greatly affected by a degraded state, for our synthetic non-trim test, we have chosen our standard sequential write test. By opting for this test and not one of our other shorter tests, the controller will not be able to compensate for being in a degraded state by using over-provisioning, caching or other similar buffers to hide the true state of the drive. To put it simply, by writing data across the entire drive, we will quickly see how big an impact this environment will have on them.
Real World Results
For a real world application we have opted for our standard Vista load time test.
These results really do speak volumes about the amount of performance Corsair has wrung from the Marvell controller. Not only is this drive able to recover from a degraded state faster than anything else we have seen before but it was also able to successfully mask its degraded state quite well. This means an end user will never actually "feel" like their Performance Pro is running slower than when it was brand new, even after a year of heavy usage. The extra cache space really does pay dividends and the payout is one bloody impressive drive for non-Trim environments.
Last edited by a moderator: