OCZ's Vertex 2, Special Sauce SF-1200 Reviewed
by Anand Lal Shimpi on April 28, 2010 3:17 PM ESTStarting with the Differences: Power Consumption
I’ll spoil the surprise up front: the Vertex 2 performs identically to Corsair’s Force drives, as expected. This is a good thing since those drives perform as well as the Vertex LE, which in turn are generally faster than Intel’s X25-M and second only to Crucial’s C300 in some cases.
Unless we stumble upon any other issues with the RC firmware, the difference between these drives amounts to power consumption.
At idle the Vertex 2 actually uses more power than Corsair’s Force F100 - 0.65W vs. 0.57W. The Vertex LE also exhibits the same lower power consumption, so I wonder if it’s related to the earlier firmware revision (I haven’t updated my LE to 3.0.5/1.05 yet).
Under load we see a larger difference between the Vertex 2 and the F100. The Corsair drive pulls 1.25W in our sequential write test compared to 0.97W from the Vertex 2. For desktop users the power consumption differences won’t matter, this is really more of an academic or notebook discussion.
Power consumption during heavy random writes is closer between the two drives, but the Force still draws a tad bit more.
For notebook users it appears to be a tradeoff - lower power consumption at idle or lower power consumption under load. I’d argue that the former is just as important, but it really varies based on usage model.
Facebook
Twitter
RSS
44 Comments
View All Comments
ScottHavens - Wednesday, April 28, 2010 - link
In the article, it was suggested that random data is not representative of what users will see. While the current sizes of drives may make that true, the importance of performance under loads of random data will become more important with time and with the growth of drive sizes. Why? Users will start to store a larger percentage of already-compressed files, like mp3s and movies, on their SSDs instead of buying additional bulk drives, and compressed files are, by nature, effectively identical to random data.ggathagan - Wednesday, April 28, 2010 - link
Anand made two important distinctions: *small* and *writes*.He wasn't referring to all random data, regardless of size, and wasn't referring to reads.
Those are important qualifications. Most mp3 files, and certainly movies fall under the *large* file size.
Additionally, the vast amount of activity with those types of files are going to be reads, not writes.
Lonyo - Wednesday, April 28, 2010 - link
Not to mention that compressed files such as XviD/etc films won't see anywhere near as much benefit from an SSD in the first place.Sure, your read/write speeds might double or triple, but when it comes to sequential activities, mechanical drives are fast. SSDs excel at random reads/writes, which large files don't have so much of, since it's typically stored in a big chunk, meaning sequential activity, not random. And that's only a copying scenario.
The point at which an SSD becomes useful for such large files will be further away than the point at which it becomes viable for a wider range of files. I would transfer my games to a large SSD long before I would start transferring compressed media files. They can stay on a mechanical for a loooooong time.
When we do finally have large enough drives that they might be the primary storage drives, I doubt Sandforce will necessarily be applying the same ideas, and if they are, they will have progressed significantly from their current state.
Talking about applying a realistic future problem to drives which exist today is meaningless when you consider how much progress has been already made up the this point, and how much progress will be made between now and when the future issue actually becomes a reality (when SSDs are affordable for mass storage purposes).
ScottHavens - Wednesday, April 28, 2010 - link
I'm not arguing about whether a particular disclaimer in the article was completely accurate. My primary point was that it's not unheard of for people to use only one drive and still have a significant portion of their data compressed, and the number of people affected by this will likely increase over time. Further, I missed a key scenario that other posters have mentioned: file/partition encryption would likely be affected as well, and it's reasonable to assume that scenario will become more common as well as disk-level encryption becomes easier and even required by some companies.Further, I should point out that the problem (insofar as it is one) by no means affects only small writes. Large reads, according to the tables, have a 20% perf hit, and large writes have a 43% perf hit.
I don't intend to denigrate SandForce's methods here, by any means. If it helps, it helps, and I'll probably get at least one of these myself. I'm just pointing out that the 'YMMV' caveat is applicable to more people and situations than some people realize.
TSnor - Wednesday, April 28, 2010 - link
Re: Encryption and point that encrypted data doesn't compress. This is true, but... the SF controller self encrypts. There is little/no point in doing software full disk encryption before sending the data to the SF controller to be encrypted. SF-1200 uses 128 bit AES which NIST counts as strong encryption.ScottHavens - Wednesday, April 28, 2010 - link
Unfortunately, the only way to use that encryption is to use the device (ATA) password. Management and real-world usage of that is a pain and not nearly as flexible as the options available with, say, BitLocker. I'd wager that most companies with OS-level encryption policies in place will want to continue with their current policies rather than make exceptions for using ATA passwords with drives like this, even if the quality of the encryption itself is just as good.beginner99 - Thursday, April 29, 2010 - link
Stupid question:Can I unplug my sandforce drive and put it in an other computer and read the data without knowing the encryption password?
if yes isn't then the drives native encryption useless?
ScottHavens - Thursday, April 29, 2010 - link
No, you'll be required to enter a password on startup.arehaas - Wednesday, April 28, 2010 - link
Most laptops, including mine, allow for only one HD. I bought a Corsair F200 (before Anand reported the compressed file issue) and planned to keep my jpg photos, mp3s, some movies on the laptop attached to a TV (or a receiver). I think this is a reasonably common scenario. Users are already dealing big time with large compressed files which are slower sequentially on Sandforce than on Indilinx.I wish Crucial fixed their firmware sooner because C300 256GB is about $50 cheaper than F200 or Vertex 2 and faster in all dimensions.
beginner99 - Thursday, April 29, 2010 - link
get a cheap small external hdd if your concerned about this. But generally I would not consider mp3's and jpgs as large files.Yes, compressed but by no means large.Yeah many small laptops only have 1 hdd/sdd. It's IMHO stupid. would be much better to have space for 2 and just ship an external dvd drive. i mean i need my drive like once every couple month. completely useless if you have to carry it around all the time. (that's one great thing about the hp envy 15) ;)