From: Jens Axboe <axboe@kernel.dk>
Date: Wed, 22 Aug 2012 18:42:46 +0000 (+0200)
Subject: example: add SSD steady state test case
X-Git-Tag: fio-2.1~57^2~64
X-Git-Url: https://git.kernel.dk/?p=fio.git;a=commitdiff_plain;h=97908e6b8161634bbc1e3702dc4b762d1e242747

example: add SSD steady state test case

Simple test case:

- Start by filling a drive with large block sequential writes
- Once that is done, start filling it with random 4k writes.

At some point the latter phase will hit steady state. Progress
is logged.

Signed-off-by: Jens Axboe <axboe@kernel.dk>
---

diff --git a/examples/ssd-steadystate.fio b/examples/ssd-steadystate.fio
new file mode 100644
index 00000000..9b914677
--- /dev/null
+++ b/examples/ssd-steadystate.fio
@@ -0,0 +1,36 @@
+# Get a decent idea about the steady state performance of an SSD.
+#
+# First we sequentially write the drive. Then we completely
+# overwrite the device again, this time randomly at 4K. The former gives
+# us a good idea of the ideal write performance, you should see flat graph
+# of steady write performance. The latter we would expect to start out at
+# approximately the same rate as the sequential fill, but at some point
+# hit a write cliff and hit steady state. The latency numbers of the steady
+# state also provide a good idea of what kind of latencies to expect when
+# the device is pushed to steady state instead of peak benchmark-like
+# numbers that are usually reported.
+#
+# Note that this is a DESTRUCTIVE test. It operates on the device itself.
+# It's not destructive in the sense that it will ruin the device, but
+# whatever data you have on there will be gone.
+#
+[global]
+ioengine=libaio
+direct=1
+group_reporting
+filename=/dev/fioa
+
+[sequential-fill]
+description=Sequential fill phase
+rw=write
+iodepth=16
+bs=1M
+
+[random-write-steady]
+stonewall
+description=Random write steady state phase
+rw=randwrite
+bs=4K
+iodepth=32
+numjobs=4
+write_bw_log=fioa-steady-state