Transcend SSD340 (256GB) Review

Performance Consistency

Performance consistency tells us a lot about the architecture of these SSDs and how they handle internal defragmentation. The reason we do not have consistent IO latency with SSDs is because inevitably all controllers have to do some amount of defragmentation or garbage collection in order to continue operating at high speeds. When and how an SSD decides to run its defrag or cleanup routines directly impacts the user experience as inconsistent performance results in application slowdowns.

To test IO consistency, we fill a secure erased SSD with sequential data to ensure that all user accessible LBAs have data associated with them. Next we kick off a 4KB random write workload across all LBAs at a queue depth of 32 using incompressible data. The test is run for just over half an hour and we record instantaneous IOPS every second.

We are also testing drives with added over-provisioning by limiting the LBA range. This gives us a look into the drive’s behavior with varying levels of empty space, which is frankly a more realistic approach for client workloads.

Each of the three graphs has its own purpose. The first one is of the whole duration of the test in log scale. The second and third one zoom into the beginning of steady-state operation (t=1400s) but on different scales: the second one uses log scale for easy comparison whereas the third one uses linear scale for better visualization of differences between drives. Click the buttons below each graph to switch the source data.

For more detailed description of the test and why performance consistency matters, read our original Intel SSD DC S3700 article.

	Transcend SSD340	JMicron JMF667H (Toshiba NAND)	JMicron JMF667H (IMFT NAND)	Samsung SSD 840 EVO mSATA	Crucial MX100
Default
25% OP

Right from the start, things do not look too promising. Compared to the reference design with the same IMFT NAND, the IO consistency is considerably lower. The reference design manages around 1,000 IOPS minimum, whereas in the SSD340 the minimum performance is around 300 IOPS. Increasing the over-provisioning helps by a bit but the consistency is still poor compared to the other value drives (like the MX100). The older firmware definitely isn't doing Transcend any favors here – quite the opposite in fact.

	Transcend SSD340	JMicron JMF667H (Toshiba NAND)	JMicron JMF667H (IMFT NAND)	Samsung SSD 840 EVO mSATA	Crucial MX100
Default
25% OP

	Transcend SSD340	JMicron JMF667H (Toshiba NAND)	JMicron JMF667H (IMFT NAND)	Samsung SSD 840 EVO mSATA	Crucial MX100
Default
25% OP

TRIM Validation

To test TRIM, I first filled all user-accessible LBAs with sequential data and continued with torturing the drive with 4KB random writes (100% LBA, QD=32) for 30 minutes. After the torture I TRIM'ed the drive (quick format in Windows 7/8) and ran HD Tach to make sure TRIM is functional.

And it is.