dc6f9571c1
This isn't a significant effort to fix, so let's just enable it to move closer to the official Python PEP 8 guidelines. Fix up the existing instances where we didn't already have two lines between functions, and re-enable the pep8 warning. Change-Id: I9cf5e7e32b9c6dfedbd1b0f9bc92951cbb2c8a0d Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/399949 Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> |
||
---|---|---|
.. | ||
fio_test.conf | ||
README | ||
run_fio_test.py | ||
run_fio_test.sh |
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