numam-spdk

History

Daniel Verkamp e50cc5fd45 scripts/check_format: check trailing whitespace Fix up the two existing instances of trailing whitespace in text files, and add a check to enforce that no new trailing whitespace is added. Change-Id: I2197bed69bb356142aa6d2e4e8261c7434dd358b Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/383291 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>		2017-10-24 17:35:23 -04: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/nvme/run_fio_test.py: fix formatting	2017-10-10 12:01:01 -04:00
run_fio_test.sh	nvme/fio_test: add nvme performance test scripts	2017-06-20 15:08:34 -04: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