How do we test?

Testenvironment

Model	Intel X25-m Gen2 34 nm	160 GByte
Motherboard	Gigabyte X38-DQ6
Chipset	Intel X38	1066 MHz
CPU	Intel Xeon 3060	2.4 GHz
Memory	Corsair Dominator 9136 DDR2	2 GByte
Graphics card	Gigabyte GeForce 7200
Storage (system)	Maxtor	160 GByte
Operating systems	Ubuntu 8.04.1 Hardy	Kernel 2.6.27-11-server
Filesystem	XFS

We think everybody reading this article can imagine the following scenario: You just bought a hard drive which according the specs sheet should transfer 120 MByte/s reading and writing. In the reviews you read about astonishing 110 MByte/s but after you put the drive into you system it feels much slower. The whole story gets even worse when you start a benchmark which does randomread/write of 4 KByte blocks. There you only get two to three MBytes/s.

Because of this we don't want to publish screenshots of standard programs like HD-Tach, HD-Tune, ... we want our tests to be

• reproducible,
• accurate
• meaningful and
• varied

We test with activated caches and NCQ (Native Command Queueing) because they're also activated under daily use. But the data size tested is always at least twice the amount of the memory.

We noticed that the measuring error is constantly within ±2%. Therefore we mention it only here.

Additionally we evaluate the S.M.A.R.T. data to assess if there are already errors.

The following table give you a brief overview to which points we turn our centre of attention.

Test	Observations
Sequential Read/Write Tests	Are the values within the specifications? Which influence has the block size? Which influence has the filesystems block size?
Random Read/Write Tests	How severe is the influence on the theoretically possible (sequential) datarate? Which influence has the block size? Which influence has the block size on the filesystem?

Linux, XFS, why?

There are different reasons why we take a operating system based on a Linux Kernel instead of a fresh Windows Vista/XP installation with all Service Packs.

• The filesystem XFS offers you a flexibility you can't get from NTFS.
• The testprogram iozone runs natively under linux.
• The test partly aims to server applications.
• Iozone gives you data on a statistical basis (error, deviation, etc.)

The filesystem is going to be built as follows:

mkfs.xfs -d sunit=64 -d swidth=128 -lsize=128m -f /dev/sda

We mounted with the following options:

mount -o rw,nouuid,usrquota,logbufs=8 /dev/sda /mnt/sda

Why do we test different block sizes?

It is important to reproduce scenarios of daily usage. Certain parameters need to be variable during the test to make a statement about the product. In our test the parameters are the different block sizes. It defines the size in KBytes which is written/read on the drive during a transaction.

With this method one can test the reading and writing of either small and big files. In a normal personal computer environment you usually don't find many files smaller than 16 KByte. The relative amount of small files is much bigger on a mail or database server. Therefore tests with small block sizes are of interest for database-based applications.

In bigger RAID arrays the hard disk cache is usually disabled and the RAID-Controller takes over the job of caching. Exactly in such setups hard drives need to be very fast when reading or writing small amounts of data. Sequential throughput isn't interesting in this case.

Page 1 - Introduction	Page 8 - Sequential write ops
Page 2 - Impressions	Page 9 - Sequential read ops
Page 3 - How do we test?	Page 10 - Random write ops
Page 4 - Sequential write KByte/s	Page 11 - Random read ops
Page 5 - Sequential read KByte/s	Page 12 - Performance Degradation
Page 6 - Random write KByte/s	Page 13 - Conclusion
Page 7 - Random read KByte/s

Discuss this article in the forum