IOPS (input/output operations per second) measures how many small random reads and writes a drive or array can service per second. It is the metric that matters for VMs, databases and mail servers, where storage handles thousands of small scattered requests rather than long sequential streams.

How do you calculate IOPS for a hard drive?

For an HDD: IOPS ≈ 1000 ÷ (average seek time in ms + average rotational latency in ms). Rotational latency is half a revolution: 4.17 ms at 7,200 RPM, 3 ms at 10,000 RPM, 2 ms at 15,000 RPM. That gives roughly 75–100 IOPS for a 7.2K drive, 125–150 for a 10K drive and 175–210 for a 15K drive. SSDs have no moving parts and deliver tens of thousands of IOPS.

How do I calculate IOPS for a RAID array?

Total raw IOPS = number of drives × IOPS per drive. Then apply the RAID write penalty: effective IOPS = raw IOPS ÷ (read% + write% × penalty). The penalty is 1 for RAID 0, 2 for RAID 1 and 10, 4 for RAID 5, and 6 for RAID 6.

What is a good IOPS number?

It depends on the workload. A light file server may be happy with a few hundred IOPS; a general-purpose virtualization host typically wants 50–100 IOPS per VM; busy OLTP databases can demand tens of thousands. Measure your current workload where possible — Windows perfmon or Linux iostat report actual IOPS.

IOPS vs throughput vs latency — what is the difference?

IOPS counts operations per second and matters for small random I/O. Throughput (MB/s) measures bulk data movement and matters for backups and media. Latency (ms) is how long a single operation takes and drives how fast applications feel. A drive can score well on one and poorly on another — HDDs stream sequential data respectably but collapse to double-digit IOPS on random work.

Does a RAID controller's cache increase IOPS?

Yes, for bursts. A controller with battery- or flash-backed write-back cache acknowledges writes as soon as they land in cache, absorbing spikes and hiding the parity write penalty. Sustained random writes still eventually hit the drives, so cache raises real-world IOPS but does not repeal the underlying math.

IOPS Calculator

Estimate the IOPS and throughput of a drive or array: pick your drives, apply the RAID write penalty, and see effective performance for your read/write mix. Sizing a full array? Use the RAID calculator for capacity, rebuild time and failure risk too.

Configuration

Drive type Sets per-drive random 4K IOPS and sequential throughput used in the estimate.

Number of drives

RAID level

Workload read / write mix

70% read

Typical: 70% read for general server workloads, ~50% for OLTP databases, 90%+ for web/file serving.

Per-drive IOPS override (optional) Have the vendor's rated 4K random IOPS? Enter it here for a tighter estimate.

Performance breakdown

Estimates assume random 4K I/O spread across all drives, no controller cache. Write-back cache absorbs bursts and raises real-world numbers; sustained workloads converge on these estimates.

Build it with PC Server & Parts

What is IOPS?

IOPS (input/output operations per second) measures how many small, random reads and writes a drive or array can service each second. It's the number that matters for virtual machines, databases, mail servers and VDI — workloads that hammer storage with thousands of scattered 4–64 KB requests. Throughput (MB/s) tells you how fast you can stream a backup; IOPS tells you how many users and VMs your storage can actually carry.

How to calculate IOPS

For a hard drive, IOPS is set by mechanics — how fast the head seeks and the platter spins:

HDD IOPS ≈ 1000 ÷ (avg seek ms + avg rotational latency ms)

Rotational latency averages half a revolution: 4.17 ms at 7,200 RPM, 3 ms at 10K, 2 ms at 15K. A 7.2K SATA drive with an 8.5 ms seek lands at 1000 ÷ (8.5 + 4.17) ≈ 79 IOPS — which is why HDD counts, not capacity, dictate array performance. SSDs have no moving parts; their IOPS come from the controller and flash parallelism.

Typical random 4K IOPS by drive type
Drive type	IOPS per drive
7.2K SATA HDD	~75–100
10K SAS HDD	~125–150
15K SAS HDD	~175–210
SATA SSD	~10,000–25,000
SAS SSD	~25,000–60,000
NVMe SSD	~90,000–1,000,000

IOPS and RAID: the write penalty

In an array, reads scale with the drive count — but every write costs extra back-end operations for mirroring or parity. That's the RAID write penalty, and it's why a 12-drive RAID 6 can post worse write IOPS than a 4-drive RAID 10:

effective IOPS = (drives × IOPS per drive) ÷ (read% + write% × penalty)

Write penalty by RAID level
RAID level	Back-end I/Os per write
RAID 0 / single drive	1
RAID 1 / RAID 10	2
RAID 5	4
RAID 6	6

Example: 8 × 15K SAS drives (200 IOPS each = 1,600 raw) in RAID 5 at a 70/30 read-write mix: 1,600 ÷ (0.7 + 0.3 × 4) ≈ 842 effective IOPS. The same drives in RAID 10: 1,600 ÷ (0.7 + 0.3 × 2) ≈ 1,231 IOPS. Planning the whole array — capacity, fault tolerance, rebuild time? Run it through our RAID calculator.

How many IOPS do I need?

Rule-of-thumb IOPS demand by workload
Workload	Typical demand
File / print server	100–500 IOPS
General VM (per guest)	50–100 IOPS
VDI desktop (per seat)	10–30 IOPS (10× at boot storms)
Exchange / mail (per 100 users)	300–600 IOPS
OLTP database	2,000–50,000+ IOPS

Where possible, measure instead of guessing: Windows perfmon (Disk Transfers/sec) or Linux iostat show what your workload really draws. Size the array for peak demand plus rebuild overhead — a degraded array loses a chunk of its performance while it recovers. Hardware-wise, IOPS ceilings also come from the controller: browse RAID controller cards with flash-backed cache, enterprise drives, or complete refurbished servers configured to your target.