Firewire and USB Performance

After looking at many options for Firewire and USB testing, we finally determined that an external USB 2.0, Firewire 400, and Firewire 800 hard disk would be a sensible way to look at USB and Firewire throughput.

Our first efforts at testing with an IDE or SATA drive as the "server" yielded very inconsistent results, since Windows XP sets up cache schemes to improve performance. Finally, we decided to try a RAM disk as our "server", since memory removed almost all overhead from the serving end. We also managed to turn off disk caching on the USB and Firewire side by setting up the drives for "quick disconnect" and our results were then consistent over many test runs.

We used 1GB of fast 3-2-2-8 system memory set up as a 450MB RAM disk and 550MB of system memory. Our standard file is the SPECviewPerf install file, which is 432,533,504 bytes (412.4961MB). After copying this file to our RAM disk, we measured the time for writing from the RAM disk to our external USB 2.0, Firewire 400, or Firewire 800 drive using a Windows timing program written for AnandTech by our own Jason Clark. The copy times in seconds were then converted into Megabits per second (Mb) to provide a convenient means of comparing throughput. Higher Rates therefore mean better performance in this particular test.

Firewire and USB Performance

Possibly the most interesting finding in our Firewire and USB throughput tests is the continued performance of an external hard drive connected to Firewire 800. Firewire 800 does make a difference and should be a standard option at this time. Our benchmarks show Firewire 800 is up to 46% faster than a drive connected to the more common Firewire 400, and about 29% faster than USB 2.0. The Intel D955XBK had the Firewire 800 option, but for reasons unknown, it was dropped on the Intel D975XBX.

Disk Controller Performance Ethernet Performance
Comments Locked

34 Comments

View All Comments

  • LoneWolf15 - Thursday, January 26, 2006 - link

    "Bad Axe" is also a city in the state of Michigan.

    http://en.wikipedia.org/wiki/Bad_Axe,_Michigan">http://en.wikipedia.org/wiki/Bad_Axe,_Michigan
  • fishbits - Thursday, January 26, 2006 - link

    That they chose to call this (or anything else) "Bad Axe" will be both the funniest and saddest thing I read all day.
  • JarredWalton - Thursday, January 26, 2006 - link

    I think it's a play off of "Bad Ass" - say it fast and "axe" sounds a lot like "ass" to me. Basically, it was a codename from Intel designed to sound cool. Love it or hate it, that's what they used. Intel has geeks working there too, it seems! :)
  • BATCH71 - Thursday, January 26, 2006 - link

    I really wanted this board to be a SLI-screamer. I guess that is not the case. Next processor will be an AMD.

Log in

Don't have an account? Sign up now