Kingston SSDNow V300 (120GB & 240GB) Reviewby Kristian Vättö on April 30, 2013 12:30 PM EST
SandForce has always had trouble with TRIM. SandForce's approach of compressing data on the fly definitely complicates things and I believe it's at least partially the reason why TRIM behaves the way it does in SandForce based SSDs. Even though TRIM doesn't work perfectly in any SandForce SSD, there are differences between drives and some do better than others.
As usual, I took a 240GB V300, secure erased it, filled it with incompressible sequential data and then tortured the drive with incompressible 4KB random writes (QD=32, LBA space 100%) for 60 minutes. I then ran AS-SSD after the torture to get dirty-state performance. Finally I TRIM'ed the drive and reran AS-SSD.
|Kingston SSDNow V300 Resiliency - AS-SSD|
|Clean||After Torture||After TRIM|
|Kingston SSDNow V300 240GB||278.2MB/s||204.7MB/s||257.6MB/s|
And the issue still persists. For the most part, this isn't a big issue because the majority of users won't store just incompressible data in their SSD (e.g. Windows is very compressible) but if you know you'll be storing lots of incompressible data (H.264 videos, MP3s or encrypted data), then going with something non-SandForce is a better option.
In terms of power consumption, the V300 does pretty well. It doesn't break any records but for example Corsair's Force GS draws more power in all of our tests. The utilization of smaller process node NAND (19nm versus 24nm) does have some impact but I wouldn't be surprised if Kingston's customization also has something to do with the lower power draw.