numam-spdk

History

Ben Walker c3b5ae0c60 build: Place fio plugins into build/fio This makes them easier to find. They are now named spdk_nvme and spdk_bdev. Signed-off-by: Ben Walker <benjamin.walker@intel.com> Change-Id: I1f6736d8f7f5b9669583731fb0b710ba54f0d50a Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2679 Community-CI: Mellanox Build Bot Community-CI: Broadcom CI Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>		2020-06-15 15:27:16 +00:00
..
fio_test.conf	nvme/fio_test: add nvme performance test scripts	2017-06-20 15:08:34 -04:00
README	scripts/check_format: check trailing whitespace	2017-10-24 17:35:23 -04:00
run_fio_test.py	scripts/perf: fix nvme perf scripts	2018-10-11 20:46:18 +00:00
run_fio_test.sh	build: Place fio plugins into build/fio	2020-06-15 15:27:16 +00:00

README

These scripts are used to perform benchmark testing with fio.
The run_fio_test.py is the main script that runs the performance test and parses the test results.
Users can populate test parameters for different fio workloads in the lists (q_depth, io_size, workload_type, mix, core_mask and run_time) at the top of the run_fio_test.py script.
The run_fio_test.py puts the test results in a csv file named <hostname>_<num ssds>_perf_output.csv.
The run_fio_test.sh script demonstrates how to invoke the run_fio_test.py script with the
input parameters: path_to_fio_conf, path_to_ioengine and num_ssds. The run_fio_test.sh script will
call the SPDK setup.sh script to unbind NVMe devices from the kernel driver and bind them to the uio driver.
We include a sample fio configuration file that includes the parameters we use in our test environment.
The run_fio_test.py will append the NVMe devices to the end of the configuration file. The number of
NVMe devices used is specified using the num_ssds parameter.

Usage: ./run_fio_test.sh