IOPS Calculator
Calculate storage IOPS from throughput, block size and access pattern.
About IOPS Calculator
For mechanical HDDs, IOPS is bounded by physical latency: the time to seek the head to the right track plus the rotational latency waiting for the target sector to pass under the head, with 1000ms divided by that total latency giving operations per second. SSDs have no moving parts, so their IOPS instead scales with how many requests can be serviced in parallel (queue depth) divided by the average latency per request — flash controllers process many requests concurrently across channels, which is why SSD IOPS is typically 100-1000x higher than HDDs despite similar or lower per-request latency.
Formulas
HDD IOPS
IOPS = 1000 / (seek_time_ms + rotational_latency_ms)
SSD IOPS
IOPS = (queue_depth / latency_ms) × 1000
Worked example
With the default values below, IOPS Calculator returns Estimated IOPS of 167. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Drive Typeone of HDD (mechanical), SSD (flash)
- HDD (mechanical)
- Average Seek Timeminimum 0 ms
- 4 ms
- Rotational Latencyminimum 0 ms
- 2 ms
- Queue Depthminimum 1
- 32
- Average I/O Latencyminimum 0.001 ms
- 0.1 ms
Results
- Estimated IOPS
- 167
- Drive Type
- HDD (mechanical)
- Total Latency per I/O
- 6.00 ms
Step by step
- 1Values used
- 2HDD IOPS
- 3SSD IOPS
- 4Estimated IOPS= 167
- 5Drive Type= HDD (mechanical)
- 6Total Latency per I/O= 6.00 ms
Assumptions and limits
- The result is derived only from the 5 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
- Figures are rounded for display to 4 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
Frequently Asked Questions
Why don't SSDs have a seek time in this calculation?
SSDs use NAND flash with no mechanical head to move — any cell can be addressed electronically in roughly constant time, so there's no seek or rotational delay analogous to an HDD's actuator arm and spinning platter.
How does queue depth increase SSD IOPS if latency per request stays the same?
Modern SSD controllers process multiple requests concurrently across parallel NAND channels, so increasing queue depth lets more requests be in flight simultaneously — doubling queue depth roughly doubles throughput until the controller's internal parallelism or the host interface bandwidth is saturated.
Is real-world IOPS usually higher or lower than this estimate?
Usually lower, because this models only device-level latency for random, uniformly-sized I/O — real workloads add file system overhead, controller/HBA queuing, RAID write penalties, and mixed block sizes, all of which reduce effective IOPS below the raw device ceiling.