Disk IOPS Calculator

Calculate disk IOPS from seek time, rotational latency, and transfer time. Compare HDD and SSD random I/O performance.

ms
0 for SSDs
ms
ms
Concurrent IOs
Effective IOPS
118.00
Base 118 × QD 1
Read IOPS
83.00
70% of effective IOPS
Write IOPS
35.00
30% of effective IOPS
Throughput
0.5 MB/s
4 KB blocks × 118.00 IOPS
IO Latency
8.470 ms
8,470.00 µs per single IO
Single IO Time
8.470 ms
Seek + rotation + transfer
Your IOPS vs Drive Types
Your Config
118.00
7,200 RPM HDD
80.00
10,000 RPM HDD
140.00
15,000 RPM HDD
180.00
SATA SSD
75,000.00
NVMe SSD
500,000.00

Drive Type Reference

Drive TypeTypical IOPSSeq. ThroughputAvg Latencyvs Yours
7,200 RPM HDD80.00120.00 MB/s12.5 ms1.48×
10,000 RPM HDD140.00170.00 MB/s7.2 ms0.84×
15,000 RPM HDD180.00210.00 MB/s5.5 ms0.66×
SATA SSD75,000.00550.00 MB/s0.1 ms0×
NVMe SSD500,000.003,500.00 MB/s0.02 ms0×
Calculation Breakdown
StepValueFormula
Single IO time8.470 msSeek + Rotation + Transfer
Base IOPS118.11000 / IO time (ms)
Queue depth multiplier×1Concurrent IO operations
Effective IOPS118.00Base IOPS × Queue Depth
Throughput0.5 MB/sIOPS × Block Size / 1024
Planning notes, formulas, and examples

About the Disk IOPS Calculator

IOPS (Input/Output Operations Per Second) is the fundamental measure of storage device performance for random access workloads. For HDDs, IOPS is primarily limited by mechanical factors: the time the read/write head takes to move (seek time) and the time for the platter to rotate to the right position (rotational latency). A typical 7,200 RPM enterprise HDD delivers about 75–100 random IOPS, while a 15,000 RPM drive might reach 180 IOPS.

SSDs eliminate mechanical latency entirely, delivering tens of thousands to hundreds of thousands of random IOPS. This dramatic difference is why SSD adoption has been transformative for database and virtualization workloads. This calculator lets you model IOPS from the physical characteristics of any storage device, showing the theoretical maximum for both random reads and writes.

When This Page Helps

IOPS is the key performance metric for databases, virtual machines, and any workload with random access patterns. This calculator derives IOPS from physical drive characteristics, helping you compare devices, validate vendor claims, and size storage for performance requirements.

How to Use the Inputs

  1. Enter the average seek time in milliseconds (HDD: 3–12 ms, SSD: 0.05–0.1 ms).
  2. Enter the rotational latency in ms (HDD: 2–4.2 ms, SSD: 0 ms).
  3. Enter the transfer time per IO in ms (typically 0.01–0.5 ms).
  4. Review the calculated IOPS.
  5. Compare HDD vs. SSD by entering typical values for each.
Formula used
IOPS = 1000 / (seek_time_ms + rotational_latency_ms + transfer_time_ms)

Example Calculation

Result: 118 IOPS

For a 7,200 RPM HDD: seek time 4.2 ms + rotational latency 4.17 ms (half rotation at 7200 RPM) + transfer time 0.1 ms = 8.47 ms per IO. 1000 / 8.47 = 118 IOPS. An SSD with 0.05 ms seek, 0 ms latency, and 0.01 ms transfer yields 16,667 IOPS—over 140× faster.

Tips & Best Practices

  • Rotational latency for an HDD equals half a rotation: (60 / RPM / 2) × 1000 ms.
  • A 7,200 RPM drive has ~4.17 ms rotational latency; 15,000 RPM has ~2.0 ms.
  • SSD IOPS are limited by controller and NAND, not mechanical factors—set seek and latency to near zero.
  • Write IOPS are typically lower than read IOPS due to erase-before-write on SSDs and write verification on HDDs.
  • RAID configurations multiply effective IOPS: RAID 10 with 4 drives provides roughly 4× read IOPS.
  • Real-world IOPS are lower than theoretical due to OS scheduling, queue depth, and workload mix.

HDD Mechanical Factors

HDD IOPS is dominated by seek time and rotational latency. Seek time varies from 0.5 ms (short stroke) to 12 ms (full stroke), averaging 3–5 ms for enterprise drives. Rotational latency of 4.17 ms (7200 RPM) or 2.0 ms (15000 RPM) is the other major component. Transfer time is negligible for small IOs.

SSD Performance Characteristics

SSDs deliver IOPS through parallelism across multiple NAND channels and dies. NVMe SSDs connect via PCIe, eliminating the AHCI overhead of SATA. A modern NVMe drive can sustain 500,000+ random read IOPS at queue depth 256. Write IOPS are typically 60–80% of read IOPS due to garbage collection overhead.

Sizing for Database Workloads

To size storage for a database, multiply the expected transactions per second by the average IOs per transaction (typically 5–20). Add 20% overhead for background tasks. This gives the minimum IOPS your storage must deliver.

Sources & Methodology

Last updated:

Frequently Asked Questions

  • It depends on the workload. A single desktop user needs 50–100 IOPS. A busy database server may need 5,000–50,000 IOPS. Virtualization hosts typically need 100–500 IOPS per VM. Enterprise NVMe SSDs can deliver 100,000–1,000,000+ IOPS.