Hardware Setup

Standard Test Bed
Playback of iPEAK Trace Files and Test Application Results
Processor: AMD Opteron 170 utilized for all tests
RAM: 2 x 1GB Corsair 3500LL PRO
Settings - DDR400 at (2.5-3-3-7, 1T)
OS Hard Drive: 1 x Western Digital 7200 RPM SATA (16MB Buffer)
System Platform Drivers: NVIDIA Platform Driver - 6.85
Video Card: 1 x Asus 7600GS (PCI Express) for all tests.
Video Drivers: NVIDIA nForce 84.21 WHQL
Optical Drive: BenQ DW1640
Cooling: Zalman CNPS9500
Power Supply: Corsair HX620W
Case: Gigabyte 3D Aurora
Operating System: Windows XP Professional SP2
Motherboard: MSI K8N Diamond Plus

Our current test bed reflects changes in the marketplace over the past six months. Based upon the continuing proliferation of dual core processors and future roadmaps from AMD and Intel signifying the end of the single core processor on the desktop in the near future, we settled on an AMD Opteron 170. This change will also allow us to expand our real world multitasking benchmarks in the near future while providing a stable platform for the next six months. We are currently conducting preliminary benchmark testing under Vista with both 2GB and 4GB memory configurations. We will offer real-world Vista benchmarks once the driver situation matures but IPEAK results will continue to be XP based as the application is not compatible with Vista.

Test Setup - Software

With the variety of disk drive benchmarks available, we needed a means of comparing the true performance of the hard drives in real world applications. While we will continue to utilize HDTach and PCMark05 for comparative benchmarks our logical choice for application benchmarking is the Intel iPeak Storage Performance Toolkit version 3. We originally started using this storage benchmark application in our Q2 2004 Desktop Hard Drive Comparison. The iPeak test can be designed to measure "pure" hard disk performance, and in this case we kept the host adapter consistent while varying the hard drive models. The idea is to measure the performance of individual hard drives with a consistent host adapter.

We utilize the iPeak WinTrace32 program to record precise I/O operations when running real world benchmarks. We then utilize the iPeak AnalyzeTrace program to review the disk trace file for integrity and ensure our trace files have properly captured the activities we required. Intel's RankDisk utility is used to play back the workload of all I/O operations that took place during the recording. RankDisk generates results in a mean service time in milliseconds format; in other words, it gives the average time that each drive took to fulfill each I/O operation. In order to make the data more understandable, we report the scores as an average number of I/O operations per second so that higher scores translate into better performance in all of our iPeak results. While these measurements will provide a score representing "pure" hard drive performance, the actual impact on the real world applications can and will be different.

Each drive is formatted before each test run and three tests are completed in order to ensure consistency in the benchmark results. The high and low scores are removed with the remaining median score representing our reported result. We utilize the NVIDIA nF4 SATA ports along with the NVIDIA IDE-SW driver to ensure consistency in our playback results when utilizing NCQ, TCQ, or RAID settings. Although we test NCQ capabilities, all of our reported results are generated with NCQ off unless otherwise noted. We will test our Deskstar 7K1000 with AAM and NCQ turned on as AAM does not noticeably impact performance and this drive performs better with NCQ on in the majority of our tests.

Our iPeak tests represent a fairly extensive cross section of applications and usage patterns for both the general and enthusiast user. We will continually tailor these benchmarks with an eye towards the drive's intended usage and feature set when compared to similar drives. In essence, although we will reports results from our test suite for all drives, it is important to realize a drive designed for PVR duty will generate significantly different scores in our gaming benchmarks than a drive designed with gaming in mind such as the WD Raptor. This does not necessarily make the PVR drive a bad choice for those who capture and manipulate video while also gaming. Hopefully our comments in the results sections will offer proper guidance for making a purchasing decision in these situations. Our iPeak Test Suite consists of the following benchmarks.

VeriTest Business Winstone 2004: trace file of the entire test suite that includes applications such as Microsoft Office XP, WinZip 8.1, and Norton Antivirus 2003.

VeriTest Multimedia Content Creation 2004: trace file of the entire test suite that includes applications such as Adobe Photoshop 7.01, Macromedia Director MX 9.0, Microsoft Windows Media Encoder 9.0, Newtek Lightwave 3D 7.5b, and others.

AVG Antivirus 7.1.392: trace file of a complete antivirus scan on our test bed hard drive.

Microsoft Disk Defragmenter: trace file of the complete defragmentation process after the operating system and all applications were installed on our test bed hard drive.

WinRAR 3.51: trace file of creating a single compressed file consisting of 444 files in 10 different folders totaling 602MB. The test is split into the time it takes to compress the files and the time it takes to decompress the files.

File Transfer: individual trace files of transferring the Office Space DVD files to our source drive and transferring the files back to our test drive. The content being transferred consists of 29 files with a content size of 7.55GB.

AnyDVD 5.9.6: trace file of the time it takes to "rip" the Office Space DVD. We first copy the entire DVD over to our source drives, defragment the drive, and then measure the time it takes for AnyDVD to "rip" the contents to our test drive. While this is not ideal, it does remove the optical drive as a potential bottleneck during the extraction process and allows us to track the write performance of the drive.

Nero Recode 2: trace file of the time it takes to shrink the entire Office Space DVD that was extracted in the AnyDVD process into a single 4.5GB DVD image.

Game Installation: individual trace files of the time it takes to install Sims 2 and Battlefield 2. We copy each DVD to our secondary test drives, defragment the drive, and then install each game to our source drive.

Game Play: individual trace files that capture the startup and about 15 minutes of game play in each game. The Sims 2 trace file consists of the time it takes to select a pre-configured character, setup a university, downtown, business from each expansion pack (pre-loaded), and then visit each section before returning home. Our final trace file utilizes Battlefield 2 and we play the Daqing Oilfield map in both single and multiplayer mode.

Feature Set: Hitachi 7K1000 Performance: HD Tach and HDTune
Comments Locked

74 Comments

View All Comments

  • Gary Key - Monday, March 19, 2007 - link

    It has worked well for us to date. We also took readings with several other programs and a thermal probe. All readings were similar so we trust it at this time. I understand your concern as the sensors have not always been accurate.
  • mkruer - Monday, March 19, 2007 - link

    I hate this decimal Byte rating they use. They say the capacity is 1 TeraByte meaning 1,000,000,000,000 Bytes, this actually translates into ~930GB or .93TB that the OS will see using the more commonly used (base 2) metric. This is the metric that people assume you are talking about. When will the drive manufactures get with the picture and list the standard Byte capacity?
  • Spoelie - Tuesday, March 20, 2007 - link

    I don't think it matters all that much, once you heard it you know it. There's not even a competitive marketing advantage or any scamming going on since ALL the drive manufacturers use it and in marketing material there's always a note somewhere explaining 1GB = blablabla bytes. So 160GB on one drive = 160GB on another drive. That it's not the formatted capacity has been made clear for years now, so I think most people who it matters for know.
  • Zoomer - Wednesday, March 21, 2007 - link

    IBM used to not do this. Their advertised 120GB drive was actually 123.xxGB, where the GB referred to the decimal giga. This made useable capacity a little over 120GB. :)
  • JarredWalton - Monday, March 19, 2007 - link

    See above, as well as http://en.wikipedia.org/wiki/SI_prefix">SI prefix overview and http://en.wikipedia.org/wiki/Binary_prefix">binary prefix overview for details. It's telling that this came into being in 1998, at which time there was a class action lawsuit occurring I believe.

    Of course, you can blame the computer industry for just "approximating" way back when KB and MB were first introduced to be 1024 and 1048576 bytes. It probably would have been best if they had created new prefixes rather than cloning the SI prefixes and altering their meaning.

    It's all academic at this point, and we just try to present the actual result for people so that they understand what is truly meant (i.e. the "Formatted Capacity").
  • Olaf van der Spek - Monday, March 19, 2007 - link

    quote:

    Hitachi Global Storage Technologies announced right before CES 2007 they would be shipping a new 1TB (1024GB) hard disk drive in Q1 of this year at an extremely competitive price of $399 or just about 40 cents per GB of storage.


    The screenshot shows only 1 x 10 ^ 12 bytes. :(

    And I'm wondering, do you know about any plans for 2.5" desktop drives (meaning, not more expensive than cheapest 3.5" drives and better access time)?
  • crimson117 - Monday, March 19, 2007 - link

    How many bytes does this drive actually hold? Is it 1,000,000,000,000 bytes or 1,099,511,627,776 bytes?


    It's interesting... it used to not seem like a huge difference, but now that we're approaching such high capacities, it's almost a 100 GB difference - more than most laptop hard disks!
  • crimson117 - Monday, March 19, 2007 - link

    I should learn to read: Operating System Stated Capacity: 931.5 GB
  • JarredWalton - Monday, March 19, 2007 - link

    Of course, the standard people decided (AFTER the fact) that we should now use GiB and MiB and TiB for multiples of 1024 (2^10). Most of us grew up thinking 1KB = 1024B, 1MB = 1024KB, etc. I would say the redefinition was in a large part to prevent future class action lawsuits (i.e. I could see storage companies lobbying SI to create a "new" definition). Windows of course continues to use the older standard.

    Long story short, multiples of 1000 are used for referring to bandwidth and - according to the storage sector - storage capacity. Multiples of 1024 are used for memory capacity and - according to most software companies - storage capacity. SI sides with the storage people on the use of mibibytes, gibibytes, etc.
  • mino - Tuesday, March 20, 2007 - link

    Ehm, ehm.
    GB was ALWAYS spelled Giga-Byte and Giga- with short "G" is a standard prefix for 10^9 since the 19th century(maybe longer).

    The one who screwed up were the software guys whoe just ignored the fact 1024!=1000 and used the same prefix with different meaning.

    SI for long ignored this stupidity.
    Lately SI guys realized software guys are too careless to accept the reality that 1024 really does not equal 1000.

    It is far better to have some standard way to define 1024-multiples and have many people use old wrong prefixes than to have no such definition at all.

    I remember clearly how confused I was back in my 8th grade on Informatics class when teacher tried(and failed back then) to explain why everywhere SI prefixes mean 10^x but in computers they mean 2^10 aka 1024.
    IT took me some 4 years until I was comfortable with power-of-something nubers enough so that it did not matter whether one said 512 or 2^9 to me.

    This prefix issue is a mess SI did not create nor caused. They are just trying to clean it up in the single possible way.

Log in

Don't have an account? Sign up now