Power Consumption

With the Vertex 4, OCZ had a fairly power hungry drive on its hands. Thankfully that's well addressed by the Vector and Barefoot 3. Idle power remains higher than I would like; Samsung clearly has the advantage there. Under load however, the Vector is indistinguishable from Samsung's SSD 840 Pro, which is quite remarkable. Only slower drives or SandForce based solutions faced with highly compressible data can offer better load power consumption. In practice, I'd expect OCZ's Vector to be among the most power efficient, high performance drives on the market under load.

Drive Power Consumption - Idle

Drive Power Consumption - Sequential Write

Drive Power Consumption - Random Write

TRIM Functionality Final Words
Comments Locked

151 Comments

View All Comments

  • dj christian - Thursday, November 29, 2012 - link

    "Now, according to Anandtech, a 256GB-labelled SSD actually *HAS* the full 256GiB (275GB) of flash memory. But you lose 8% of flash for provisioning, so you end up with around 238GiB (255GB) anyway. It displays as 238GB in Windows.

    If the SSDs really had 256GB (238GiB) of space as labelled, you'd subtract your 8% and get 235GB (219GiB) which displays as 219GB in Windows. "

    Uuh what?
  • sully213 - Wednesday, November 28, 2012 - link

    I'm pretty sure he's referring to the amount of NAND on the drive minus the 6.8% set aside as spare area, not the old mechanical meaning where you "lost" disk space when a drive was formatted because of base 10 to base 2 conversion.
  • JellyRoll - Tuesday, November 27, 2012 - link

    How long does the heavy test take? The longest recorded busy time was 967 seconds from the Crucial M4. This is only 16 minutes of activity. Does the trace replay in real time, or does it run compressed? 16 minutes surely doesnt seem to be that much of a long test.
  • DerPuppy - Tuesday, November 27, 2012 - link

    Quote from text "Note that disk busy time excludes any and all idles, this is just how long the SSD was busy doing something:"
  • JellyRoll - Tuesday, November 27, 2012 - link

    yes, I took note of that :). That is the reason for the question though, if there were an idea of how long the idle periods were we can take into account the amount of time the GC for each drive functions, and how well.
  • Anand Lal Shimpi - Wednesday, November 28, 2012 - link

    I truncate idles longer than 25 seconds during playback. The total runtime on the fastest drives ends up being around 1.5 hours.

    Take care,
    Anand
  • Kristian Vättö - Wednesday, November 28, 2012 - link

    And on Crucial v4 it took 7 hours...
  • JellyRoll - Wednesday, November 28, 2012 - link

    Wouldn't this compress the QD during the test period? If the SSDs recorded activity is QD2 for an hour, then the trace is replayed quickly this creates a high QD situation. QD2 for an hour compressed to 5 minutes is going to play back at a much higher QD.
  • dj christian - Thursday, November 29, 2012 - link

    What is QD?
  • doylecc - Tuesday, December 4, 2012 - link

    Que Depth

Log in

Don't have an account? Sign up now