Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: OCZ Agility SATA 2.0 SSD 120GB

  1. #11
    Join Date
    Mar 2009
    Posts
    10

    Default

    Quote Originally Posted by Jonno View Post
    Firstly, the Agility series ships with the 1.30 firmware version, which is availible as an update to the Vertex, while your Vertex only was updated to 1.10.
    Yes.

    Quote Originally Posted by bugmenot View Post
    The reason why 120gb OCZ agility beats 60gb OCZ vertex is because they are different sizes.
    Yes.

    Thanks for pointing out these obvious flaws in this benchmark. Very, very sloppy.

    Also to note is that the 1.30 version of OCZ SSD firmware for the Agility and Vertex introduce a concept called "Garbage Collection". The GC routines kick in when the drive is otherwise idle and is used to organize/collect data on the flash so that it will be able to do it in the most efficient/fastest way possible. The 1.30 firmware has a very early version of GC that can take a lot of idle time to take effect. The next released firmware should be much better in this regard. PCPer has an article which tests an early release of this new firmware which shows how it can help.

    At the very least, both SSDs should have been wiped clean using the tools available from OCZ to make sure both were in the same starting state.

  2. #12
    Join Date
    Nov 2008
    Posts
    77

    Post

    Quote Originally Posted by d2kx View Post
    TRIM is supported by ext4 (dunno about ext3) since Linux 2.6.30 or 2.6.31. But there is still no SSD avaible that supports this command. Firmware updates for Intel and probably the Indilinx are coming September/October-ish.
    While technically true, it's not the whole truth. While ext4 (but currently not ext3) does issue TRIM commands in what the developers believe is the correct places, the VFS layer in the kernel does not pass it down to the drive, as that is considered dangerous to do without testing it on actual hardware. So just updating the firmware when it's released won't be enough, you'll need a new kernel too. The VFS will defenitely not get TRIM support before 2.6.32, most likely not until 2.6.33. So most end users won't see it until the Spring 2010 release of their favorite distribution.

  3. #13
    Join Date
    Nov 2008
    Posts
    77

    Post

    Quote Originally Posted by drees View Post
    Also to note is that the 1.30 version of OCZ SSD firmware for the Agility and Vertex introduce a concept called "Garbage Collection". The GC routines kick in when the drive is otherwise idle and is used to organize/collect data on the flash so that it will be able to do it in the most efficient/fastest way possible. The 1.30 firmware has a very early version of GC that can take a lot of idle time to take effect. The next released firmware should be much better in this regard. PCPer has an article which tests an early release of this new firmware which shows how it can help.
    Well, garbage collecting is great, but if all logical blocks are written to neither write combining nor garbage collection will be very usefull, as ther will be no room to manouver in. And without TRIM support all logical blocks will be written to in relatively short order (depending on disk usage of course). Combining this with TRIM support in a future firmware release will be great though. Perhaps even enough to match Intel X-25 M G1 performance, though only time will tell for sure.

    Quote Originally Posted by drees View Post
    At the very least, both SSDs should have been wiped clean using the tools available from OCZ to make sure both were in the same starting state.
    Well, either that or both drives should have been dd:ed to the same "used" starting state. That would also make them comparable, though at lower (and more realisitic) performane.

  4. #14
    Join Date
    Mar 2009
    Posts
    10

    Default

    Quote Originally Posted by Jonno View Post
    Well, garbage collecting is great, but if all logical blocks are written to neither write combining nor garbage collection will be very usefull, as ther will be no room to manouver in. And without TRIM support all logical blocks will be written to in relatively short order (depending on disk usage of course). Combining this with TRIM support in a future firmware release will be great though. Perhaps even enough to match Intel X-25 M G1 performance, though only time will tell for sure.
    I don't know - it seems like the PCPer report shows that as long as the drives have enough time to GC, it is enough to regain full write performance. Is it less than optimal? Probably - I'd imagine that with TRIM support less time will be needed for GC.
    Quote Originally Posted by Jonno View Post
    Well, either that or both drives should have been dd:ed to the same "used" starting state. That would also make them comparable, though at lower (and more realisitic) performane.
    Even a dd wipe is not always enough to bring drives to the same state from differing starting states - I'm pretty sure that Anandtech and others found that out as well.

  5. #15
    Join Date
    Feb 2009
    Posts
    10

    Default

    That's because a 120G drive has perhaps 130G of blocks available to it.
    This extra space (I don't remember the exact amount of extra space given) allows the drives to write and move blocks about if it needs to combine many blocks to delete them etc, speeding it up.

    When dd-ing a drive a couple of times over, this area will probably get eaten into - while dd-ing a fresh drive only once will leave this spare space alone.

    You also have the firmware storing reference tables etc, and the more that get's messed up, the worse the performance is (another thing I guess 'GC' does on the newer firmwares).

    I've only JUST got 2 30G vertex drives right now (afraid to partition/format them as I'm not 100% sure if I have the 512K alignment correct) - and if these drives are as good as they look then I might get 2 of these and compare - although for a PC you'd want drives around the 120G mark.
    I could do some preliminary file creation / random file copy tests from a ramfs filesystem (so you get rid of that useless read / CPU bound problems) like I did to test my current Core2 (yes, I know - but they're RAID-ed and I'd prefer the nice new Vertex's in my laptops ta :P).

    It strikes me as odd that a Vertex couldn't out-perform a normal rotary drive in a few of these tests - it screams "something wrong here" to me.

    Anyway - PEACE!

    --
    Paul

  6. #16
    Join Date
    Aug 2007
    Posts
    6,598

    Default

    That's a good idea to bench a fresh and a used drive. Even if that TRIM command is not directly available in Linux i am sure that there are tools the can reset the drive state.

  7. #17
    Join Date
    Jan 2007
    Location
    Germany
    Posts
    2,093

    Default

    The Indilinx SSDs (OCZ, SuperTalent, etc.) are getting TRIM support within this week (SuperTalent has, OCZ gets tomorrow). Hopefully it'll be supported by Linux 2.6.32 then.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •