IOPS
Observed IOPS is the number of completed input/output operations divided by the measurement duration at a specified system boundary.
State the counted operation types, elapsed interval, request sizes and treatment of errors; an offered request rate is not a completion rate. Linux block statistics separately count completed requests and merged requests, so application and device counts need not agree [3]. For the same successful data-transfer operations and interval, bytes/s equals IOPS multiplied by the operation-weighted mean completed size; this is accounting, not a prediction of device capacity [4]. Directional fio runtime denominators and interval-sampled iops_mean are distinct reporting quantities; establish a common observation window before combining rates [5].
Relations
- related
- Queue depth, Storage latency, Storage throughput, I/O request size, Little's law, Sequential I/O, Random I/O, Microbenchmark, Token bucket, Leaky-bucket meter
Limitations
- An IOPS figure without its workload, measurement boundary and latency distribution does not establish performance for another workload. [2, 4]
Citations
- fio documentation: blocksize, bssplit, I/O depth and interpreting the output; online manual reviewed 13 October 2026.
- Linux kernel documentation: I/O statistics fields; completed requests, merged requests and sectors.
- Hesela: IOPS, bytes and average occupancy; synthetic accounting examples.
- fio 3.41 source: stat.c, add_ddir_lat_json and add_ddir_status_json; latency sample counts and directional runtime denominators.