Skip to content

fio — Flexible I/O Tester ​

Tool: fioStatus: Not proven on hardware

NOTE

Status: implemented and unit-tested, not proven on hardware. See the implementation status table. Command examples on this page show the intended workflow; the param block of each script is the authority for parameter names. Not proven on a live cluster.

fio provides fine-grained storage I/O benchmarking with precise control over block sizes, queue depths, I/O engines, and workload patterns. It runs inside Linux VMs on the Azure Local cluster via Ansible deployment.


Run This Test ​

Prerequisites ​

  • Linux VMs deployed on your Azure Local cluster
  • Ansible 2.14+ installed on your management workstation
  • SSH key-based access to Linux VMs
  • Framework prerequisites completed

Step 1 — Install fio on target VMs ​

powershell
.\tools\fio\scripts\Install-Fio.ps1 `
    -ClusterName "hci01.corp.infiniteimprobability.com" `
    -Nodes @("hci01-node1", "hci01-node2")

This triggers an Ansible playbook that installs the fio package on the specified Linux VMs.

Step 2 — Run a workload profile ​

powershell
.\tools\fio\scripts\Start-FioTest.ps1 `
    -ClusterName "hci01.corp.infiniteimprobability.com" `
    -Nodes @("hci01-node1", "hci01-node2") `
    -Profile "random-read" `
    -DurationSeconds 300

Step 3 — Collect results ​

powershell
.\tools\fio\scripts\Collect-FioResults.ps1 `
    -ClusterName "hci01.corp.infiniteimprobability.com" `
    -Nodes @("hci01-node1", "hci01-node2") `
    -RunId "<run-id-from-previous-step>"

When to Use fio vs VMFleet ​

ScenarioUse fioUse VMFleet
Linux VM storage performance✅
Fine-grained I/O parameter control✅
Fleet-scale Windows HCI storage load✅
Data integrity verification✅
I/O scheduler / queue depth testing✅

Key Capabilities ​

  • Job file-based workload definition for reproducible tests
  • Multiple I/O engines — libaio, io_uring, Windows IOCP
  • JSON output for automated parsing and reporting
  • Verification mode for data integrity testing
  • Client/server mode for distributed I/O testing across nodes

What You Get ​

After a test completes, you will have:

  • JSON output per node with IOPS, bandwidth (KB/s), and latency percentiles
  • Aggregated metrics across all nodes
  • Reports in PDF, DOCX, and/or XLSX format

File Locations ​

ComponentPath
Scriptstools/fio/scripts/
Workload Profilestools/fio/config/profiles/
Ansible Playbookstools/fio/playbooks/
Alert Rulestools/fio/monitoring/alert-rules.yml
Report Templatestools/fio/reports/templates/
Teststools/fio/tests/
Logstools/fio/logs/

Deep Dive ​

TopicPage
Ansible deployment detailsInstallation
Profile parameters and tuningWorkload Profiles
Alert rules during test runsMonitoring
Report formats and templatesReporting
Common errors and fixesTroubleshooting

Automate This Test ​

To run fio tests on a schedule or as part of a CI/CD workflow, see CI/CD Pipelines. The pipeline calls the same scripts listed above.

Released under the MIT License.