14c0f94c88
verify.state files are not very useful because we fail the tests at any first failure. If there was something wrong with IO verification then autotest.sh would fail. Fio files with metrics output (IOPS, BW, latency, etc) are also not very useful as per-patch tests are not focused on benchmarking. Fixes #2546 Signed-off-by: Kamil Godzwon <kamilx.godzwon@intel.com> Change-Id: I33fbe2fb0749d840f08ffe0d606d206268140991 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/13019 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
25 lines
256 B
Plaintext
25 lines
256 B
Plaintext
[global]
|
|
ioengine=libaio
|
|
runtime=10
|
|
filename=
|
|
group_reporting
|
|
thread
|
|
numjobs=1
|
|
direct=1
|
|
do_verify=1
|
|
verify=md5
|
|
verify_backlog=1024
|
|
verify_state_save=0
|
|
|
|
[randwrite]
|
|
stonewall
|
|
rw=randwrite
|
|
bs=512k
|
|
iodepth=256
|
|
|
|
[randrw]
|
|
stonewall
|
|
rw=randrw
|
|
bs=128k
|
|
iodepth=64
|