kata-containers/tests/metrics/storage
stevenhorsman 58672068ff shellcheck: Fix shellcheck SC2145
> Argument mixes string and array. Use * or separate argument.

- Swap echos for printfs and improve formatting
- Replace $@ with $*
- Split arrays into separate arguments

Signed-off-by: stevenhorsman <steven@uk.ibm.com>
2025-03-04 09:35:46 +00:00
..
blogbench_dockerfile metric: Upgrade blogbench to 1.2 2024-07-17 11:32:09 -07:00
fio-dockerfile metrics: FIO ci test enablement 2023-10-30 09:42:54 -06:00
web-tooling-dockerfile metrics: Adds blogbench and webtool metrics tests 2023-07-04 14:38:52 -06:00
blogbench.sh metrics: Update container name in blogbench test 2024-07-01 19:28:16 +00:00
fio_test.sh metrics: FIO ci test enablement 2023-10-30 09:42:54 -06:00
README.md metrics: removal of reference in the documentation to the dax test. 2023-10-10 15:55:59 -06:00
webtooling.sh shellcheck: Fix shellcheck SC2145 2025-03-04 09:35:46 +00:00

Kata Containers storage I/O tests

The metrics tests in this directory are designed to be used to assess storage IO.

Blogbench test

The blogbench script is based on the blogbench program which is designed to emulate a busy blog server with a number of concurrent threads performing a mixture of reads, writes and rewrites.

Running the blogbench test

The blogbench test can be run by hand, for example:

$ cd metrics
$ bash storage/blogbench.sh

fio test

The fio test utilizes the fio tool, configured to perform measurements upon a single test file.

The test spawns 8 jobs that exercise the I/O types sequential read, random read, sequential write and random write, while collecting 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.

The results show the average bandwidth and average number of IOPS per I/O type in JSON format.

The fio test can be run by hand, for example:

$ cd metrics
$ bash storage/fio_test.sh