simple-fio_v2

The purpose of this software is to provide a simple mechanism to perform fio tests on Openshift Data Foundation (ODF) without the need for additional configurations.

This repo is an improved version of simple-fio and will eventually replace it. The test architecture has been revamped to separate the initial configuration + prefill from testing.

In this version we support testing on native ODF and also ODF on HCP clusters.

How to run

1. git clone https://github.com/bose-abhishek/simple-fio_v2.git
2. cd simple-fio_v2/
3. Edit config file and set the appropriate parameters required. Described in detail in the next section.
4. Add consumers in the consumers.lst if using HCP.
5. sh 01_prepare_setup.sh
6. Once the prefill is complete, execute sh 02_run_tests.sh
7. Once the test is over, execute the delete script (sh delete_simple_fio.sh) to delete the test setup (fio server and client pods).
8. To delete the project, execute the nuke script. This will delete the namespace, fio storage along with all the stored data (sh nuke_simple-fio.sh).

Test Configuration

To execute a fio test, one needs to only change the parameters in the config.file. There are three sections in the config.file:

1. OCS Parameters

   • platform: This option is to select on which platform the test will be executed. It can be either the native ODF (bm) or in the Hosted Control Plane.
     • options: bm | hcp
   • storage_type: This defines the undelying storage class to be used.
     • options: ocs-storagecluster-ceph-rbd | ocs-storagecluster-cephfs

2. FIO Execution Parameters

   • server: Number of fio server pods (usually this equals to the number of ODF workers or multiples of it). FIO test is actually executed on it, RBD volumes or CephFS mounts are present in these pods.
   • sample: Number of iterations of the test
   • prefill: To perform prefill or not for RBD volumes
     • options: true | false
   • storage(Gi): size of each PVC (should be larger than 'numjob x fio volume/file size')

3. FIO parameters: These parameters are used exactly as defined in the FIO documentation

   • direct: If value is true, use non-buffered I/O. This is usually O_DIRECT.
   • rw: Type of I/O pattern. Multiple workloads can be specified at a time. Workloads will run sequentially as mentioned in the config file.
     • rw=read | write | randread | randwrite | randrw
   • bs: The block size in bytes used for I/O units. Unlike fio, here multiple block sizes can be mentioned with space separated.
     • bs=8k 16k
   • numjobs: Create the specified number of clones of this job. Each clone of job is spawned as an independent thread or process.
   • time_based: If set, fio will run for the duration of the runtime specified even if the file(s) are completely read or written.
     • time_based=0 | 1
   • runtime: Limit runtime. The test will run until it completes the configured I/O workload or until it has run for this specified amount of time, whichever occurs first. The value is interpreted in seconds.
   • size: File or block size.
   • iodepth: Number of I/O units to keep in flight against the file
   • log_avg_msec: Setting this option makes fio average the each log entry over the specified period of time, reducing the resolution of the log. This defines the granularity of the fio logs and can be changed according to test requirements. As a rule of thumb, it can be set as:
     • log_avg_msec=5000 # 5 seconds for 5/10 minute jobs
     • log_avg_msec=1000 # 10 seconds for more than 10 minute jobs

• Apart from the above mentioned fio parameters, few of the parameters are automatically set in the fio job file depending on the workload type.
  • When rw is set as write, fsync_on_close=1 and create_on_open=1 is applied.
  • When rw is set as any random workload, randrepeat=0 and allrandrepeat=0 is applied.