USB 3.0 Backup

Our backup testing takes a typical set of user files – specifically just under 8000 files across 4 GB, some large files but mostly small.  For USB 3.0 testing, these files are copied from a 4 GB RAMDisk onto an OCZ Vertex3 which is connected via a SATA 6 Gbps to USB 3.0 device.  We use all the USB 3.0 protocols available - the UASP protocol that the ASMedia controller on our test bed affords as well as the chipset driven Intel USB 3.0 under ASUS' Turbo mode.  The copy test is conducted using DiskBench, a copying tool with accurate copy timing.

USB 3.0 Copy Test, ASMedia + UASP

USB 3.0 Copy Test, ASMedia

USB 3.0 Copy Test, Intel + Turbo

USB 3.0 Copy Test, Intel Chipset

Across the result range, no matter which protocol is used, our copy testing shows up to a 7% decrease in copy times over the USB 3.0 protocol moving from DDR3-1333 to DDR3-2133.  In some cases, such as using Intel Turbo mode, the timing levels out around DDR3-1866, but in the case of UASP, the DDR3-2133 C9 kit provides the best result.  Interesting to note that in the case of UASP, having a smaller CL value is more important than having a larger speed value.

Thunderbolt Backup

Similar to our USB 3.0 Backup test, Thunderbolt testing carries the same files directly through to our LittleBig Disk which contains two 120 GB Intel SSDs in RAID-0.  The copy test is conducted using DiskBench, a copying tool with accurate copy timing.

Thunderbolt Copy Test

Thunderbolt tests are never as consistent as USB timing – the results shown are the average of the best three obtained.  Typically the best results come after leaving the Thunderbolt device for 30 seconds or longer after the last copy test as the TB device does an amount of post processing after the data has officially been sent.  Nevertheless, a gradual decrease in copy times is exhibited from DDR3-1333 to DDR3-2400.

Gaming Tests: Portal 2, Batman AA, Overall IGP Conversion, Compression and Computation
Comments Locked

114 Comments

View All Comments

  • andrewaggb - Friday, October 19, 2012 - link

    Fair enough :-)
  • HisDivineOrder - Thursday, October 18, 2012 - link

    You "remember" getting your first memory kit and it was for a E6400. You act like that's just this classic thing.

    I remember getting a memory kit for my Celeron 300a. I remember getting a memory kit for my AMD K6 with 3dNow!.

    Wow, I'm old.
  • silverblue - Thursday, October 18, 2012 - link

    I remember getting a 64MB PC100 DIMM in 2000... it was pretty much £1 a MB. Made a difference, so it was *gulp* worth it.
  • StormyParis - Thursday, October 18, 2012 - link

    Very interesting read. Thank you.
  • rscoot - Thursday, October 18, 2012 - link

    I remember paying upwards of $400 for a pair of matched 2x512MB Kingston HyperX modules with BH-5 chips. Those were the days! 300MHz at 2-2-2-5 1T in dual channel if you could put enough volts through them. Nowadays I don't think memory matters nearly as much as it did back then.
  • superflex - Thursday, October 18, 2012 - link

    Your first kit was an E6400?
    Let me know when you get hair down there.
    My first computer was an Apple IIe in 1984, and my first build was an Opteron 170 with 400 MHz 2,2,2,5 DDR.
  • Magnus101 - Thursday, October 18, 2012 - link

    Once again this only confirms that memory speed makes no real world difference.
    I mean, who in their right mind use the integrated GPU on an expensive i7-system to play metro-2033 with single digit framerate?
    The only thing standing out is the Winrar compression, but, how many use winrar for compression?
    Yes to decompress files it is very common but I only remember using it 2-3 times in my whole life to compress my own files.
    So that isn't important to most users, except for the ones that actually use winrar to compress files.
    And I don't get why the x264 encoding seemed like a big deal. The differences were very small.

    It's beem the same story all the way back to the late 90;s were tests between sdr memory at 100 and 133 MHz or at different timings showed no differences in real life applications in contrast to synthetics.

    But sure, if you are building a new system and choose between, let say 1333 or 1600, then a $5 difference is a no brainer.
    Then again, it would make no noticeable difference anyway.
  • silverblue - Thursday, October 18, 2012 - link

    Here's one - will it affect QuickSync in any way?
  • twoodpecker - Monday, October 22, 2012 - link

    I'd be interested in QuickSync results too. In my experience, not proven, it makes a big difference. I adjusted my memory speeds from 1600 to 2000 and noticed at some point that encoding is 25x instead of 15x. This might be due to different factors though, like software optimizations, because I didn't benchmark after adjusting mem speeds.
  • Geofram - Thursday, October 18, 2012 - link

    I don't believe he's implying that single digit frame rates on a game are going to real-life usable for anyone. I believe the point of the test was simply: "Lets take a system that is generally fast and put it in a situation where the IGP is being stressed. This will be the best-case scenario for faster RAM helping it. Lets see if it does".

    To me the idea was not showing everyone everyday situations where faster RAM will help them, instead it was to see where those situations might lay, by setting up a stressful situation and seeing the results. Most of the results were extremely small differences.

    I agree it's not a noticeable difference in most cases. It doesn't make me feel like I should get rid of PC1333 RAM. I don't fault the logic for the tests used however. It was nice to see someone actually comparing the slight differences caused by RAM speed.

Log in

Don't have an account? Sign up now