metrics: removal of reference in the documentation to the dax test.

This PR removes the reference in the documentation to the DAX
subtest of the FIO benchmark, because this metric is currently
WIP.

Fixes: #8159

Signed-off-by: David Esparza <david.esparza.borquez@intel.com>
(cherry picked from commit 89c9454fca)
Signed-off-by: Greg Kurz <groug@kaod.org>
This commit is contained in:
David Esparza 2023-10-09 15:07:51 -06:00 committed by Greg Kurz
parent 5d911db5e2
commit 0e0aabfd87

View File

@ -16,12 +16,16 @@ $ bash storage/blogbench.sh
``` ```
## `fio` test ## `fio` test
The `fio` test utilises the [fio tool](https://github.com/axboe/fio), configured The `fio` test utilizes the [fio tool](https://github.com/axboe/fio), configured to perform measurements upon a single test file.
to perform measurements upon a single test file.
The test configuration used by the script can be modified by setting a number of The test spawns 8 jobs that exercise the I/O types `sequential read`, `random read`, `sequential write` and `random write`, while collecting
environment variables to change or over-ride the test defaults. data using a block size of 4 Kb, an I/O depth of 2, and uses the `libaio` engine on a workload with a size of 10 gigabytes for a period of
10 seconds on each I/O type.
## DAX `virtio-fs` `fio` Kubernetes tests The results show the average bandwidth and average number of IOPS per I/O type in JSON format.
[Test](fio-k8s/README.md) to compare the use of DAX option in `virtio-fs`. The `fio` test can be run by hand, for example:
```
$ cd metrics
$ bash storage/fio_test.sh
```