Random Performance – Iometer (IOPS/latency), YAPT (random)

We are trying something different here. Folks tend to not like to click through pages and pages of benchmarks, so I'm going to weed out those that show little to no delta across different units (PCMark). I'm also going to group results performance trait tested. Here are the random access results:

Iometer:

Iometer is an I/O subsystem measurement and characterization tool for single and clustered systems. It was originally developed by the Intel Corporation and announced at the Intel Developers Forum (IDF) on February 17, 1998 – since then it got wide spread within the industry. Intel later discontinued work on Iometer and passed it onto the Open Source Development Lab (OSDL). In November 2001, code was dropped on SourceForge.net. Since the relaunch in February 2003, the project is driven by an international group of individuals who are continuously improving, porting and extend the product.

Iometer – IOPS

It is clear here that the 8TB Red comes in as the highest 5400 RPM performer in all of our Iometer results, even nipping at the heels of the 4TB Black and RE in some areas.

Iometer – Average Transaction Time

This test is being phased out in favor of Latency Percentile testing (on the next page).

YAPT (random)

YAPT (yet another performance test) is a benchmark recommended by a pair of drive manufacturers and was incredibly difficult to locate as it hasn't been updated or used in quite some time.  That doesn't make it irrelevant by any means though, as the benchmark is quite useful.  It creates a test file of about 100 MB in size and runs both random and sequential read and write tests with it while changing the data I/O size in the process.  The misaligned nature of this test exposes the read-modify-write performance of SSDs and Advanced Format HDDs.

YAPT is a 'misaligned' test, in that it does not adhere to 4k boundaries. This causes some drives to behave oddly, or in the case of the 8TB Red on random writes, I suspect it got caught trying to flush its larger buffer to disk later in that particular sequence.

« PreviousNext »