IOPS Calculator
Random read, write and mixed IOPS of a drive or RAID array, MB/s at any block size, and how many drives a target needs. Sizing capacity and rebuild risk too? Use the RAID calculator.
Estimate IOPS and throughput
Pick the drives and the RAID level, set your read/write share and block size. SSD reads and writes are counted separately, as their datasheets rate them.
- Datasheet figuresRead and write IOPS per drive class
- IOPS to MB/sThroughput at the block size you set
- Servers that fitChassis with enough bays, with live prices
- Mixed IOPS
- 842
- Read IOPS
- 1,600
- Write IOPS
- 400
- Throughput
- 3.4 MB/s
Performance, estimated
- Array
- 8 × 900 GB 15K SAS HDD · RAID 5
- IOPS per drive
- 200 read / 200 write
- Write penalty
- ×4
- Mixed IOPS at 70% read
- 842
- Throughput at 4 KiB
- 3.4 MB/s
- Sequential read
- 1.75 GB/s
- Sequential write
- 1.75 GB/s
Capped at about 7 GB/s: one PCIe 3.0 x8 RAID card or HBA carries no more.
Each host write costs 4 drive operations in RAID 5. For write-heavy VMs or databases, compare RAID 10 or a faster drive tier.
Sizing
- General-purpose VMs at about 75 IOPS each
- 11
- Drives for your target
- Usable capacity
- 5.73 TiB of 6.55 TiB raw (6.3 TB decimal)
Random I/O spread across all drives, no controller cache. Write-back cache lifts short bursts; sustained load settles near these figures.
Servers that take 8 × 2.5″ drives
Chassis with enough bays for these drives, priced from today's catalog. Choose CPUs, memory and the drives on the next page.
| Server | Drive bays | Chassis from |
|---|
No single chassis in our catalog takes this many drives of this size. Split the array across two servers, add a disk shelf, or send us the layout.
- Drives & parts
- Hard drives
- SAS drives
- RAID cards
- Drive trays
- Tray Finder
What is IOPS?
IOPS (input/output operations per second) counts how many small reads and writes a drive or array completes each second. It is the number that decides how many virtual machines, database users, mailboxes or VDI desktops your storage can carry, because those workloads hit it with thousands of scattered 4–64 KiB requests. Throughput (MB/s) tells you how fast a backup streams; IOPS tells you how many users the array serves.
How to calculate IOPS for a drive
A hard drive's IOPS are set by mechanics: how fast the head seeks and the platter turns.
HDD IOPS ≈ 1000 ÷ (average seek ms + average rotational latency ms)
Rotational latency is half a revolution: 4.17 ms at 7,200 RPM, 3 ms at 10K and 2 ms at 15K. A 7.2K drive with an 8.5 ms seek lands at 1000 ÷ (8.5 + 4.17) ≈ 79 IOPS, which is why the number of hard drives, not their capacity, sets an array's speed. SSDs have no moving parts; their IOPS come from the controller and flash, and their writes run several times slower than their reads.
| Drive | Read IOPS | Write IOPS | Sequential |
|---|---|---|---|
| 7.2K SATA or SAS hard drive | 75–80 | 75–80 | 180–270 MB/s |
| 10K SAS hard drive | about 140 | about 140 | about 220 MB/s |
| 15K SAS hard drive | about 200 | about 200 | about 250 MB/s |
| Enterprise SATA SSD | 75,000–98,000 | 25,000–30,000 | about 530 MB/s |
| 12 Gb/s SAS SSD | 180,000–450,000 | 60,000–90,000 | 1,000–2,100 MB/s |
| U.2 NVMe SSD | 400,000–1,000,000 | 80,000–180,000 | 3,000–6,900 MB/s |
SSD datasheets measure at deep queues (QD32 and up), so sustained mixed workloads run lower. The calculator takes the low end of each range; if you know your exact drive, enter its figures under "Your own figures".
RAID IOPS: the write penalty
In an array, reads spread across every drive, but each write costs extra drive operations for the mirror copy or the parity: the RAID write penalty. That is why a 12-drive RAID 6 can post lower write IOPS than a 4-drive RAID 10.
effective IOPS = drives × IOPS per drive ÷ (read share + write share × penalty)
| RAID level | What one write does | Penalty |
|---|---|---|
| RAID 0, single drive | Writes the block | 1 |
| RAID 1, RAID 10 | Writes both copies | 2 |
| RAID 5, RAID 50 | Reads data and parity, writes both | 4 |
| RAID 6, RAID 60 | Reads data and two parities, writes all three | 6 |
Example: eight 15K SAS drives (200 IOPS each, 1,600 raw) in RAID 5 at 70% reads: 1,600 ÷ (0.7 + 0.3 × 4) ≈ 842 IOPS. The same drives in RAID 10: 1,600 ÷ (0.7 + 0.3 × 2) ≈ 1,231 IOPS. For SSDs the calculator weighs each read and write by the drive's own read and write IOPS, since an SSD completes three to five times fewer random writes than reads. Planning capacity, fault tolerance and rebuild time as well? Run the array through the RAID calculator.
Convert IOPS to MB/s
Throughput is IOPS multiplied by the size of each operation. Type either number:
= =
MB/s = IOPS × block size in bytes ÷ 1,000,000
IOPS = MB/s × 1,000,000 ÷ block size in bytes
| IOPS | Block size | Throughput |
|---|---|---|
| 10,000 | 4 KiB | 41 MB/s |
| 10,000 | 64 KiB | 655 MB/s |
| 50,000 | 8 KiB | 410 MB/s |
| 200 | 1 MiB | 210 MB/s |
A drive reaches its peak IOPS at small blocks and its peak MB/s at large ones: a hard drive doing 200 random 4 KiB reads moves under 1 MB/s, yet streams 250 MB/s sequentially. Quote IOPS with its block size, and MB/s with its access pattern.
How many IOPS do I need?
| Workload | Typical demand |
|---|---|
| File and print server | 100–500 IOPS |
| General-purpose VM, per guest | 50–100 IOPS |
| VDI desktop, per seat | 10–30 IOPS, 10× at boot storms |
| Exchange or mail, per 100 users | 300–600 IOPS |
| OLTP database | 2,000–50,000+ IOPS |
Measure where you can: Windows Performance Monitor (Disk Transfers/sec) or Linux iostat show what the workload really draws. Size for the peak plus headroom for a rebuild, which takes a share of the array's speed while it runs. Ceilings also come from the controller: browse RAID controller cards with a flash-backed cache, enterprise SSDs, or refurbished servers configured to your target. Adding drives to an existing server? The Drive Tray & Caddy Finder lists the caddy part numbers by model.
IOPS calculator questions
What is IOPS?
IOPS (input/output operations per second) counts how many small reads and writes a drive or array completes each second. It decides how many virtual machines, database users or mailboxes storage can carry, because those workloads issue thousands of small scattered requests rather than long streams.
How do you calculate IOPS for a hard drive?
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 about 75–80 IOPS for a 7.2K drive, about 140 for 10K and about 200 for 15K.
How do I calculate IOPS for a RAID array?
Reads scale with the number of drives. Each host write costs extra drive operations, the write penalty: 1 for RAID 0, 2 for RAID 1 and 10, 4 for RAID 5 and 6 for RAID 6. For hard drives, effective IOPS = drives × IOPS per drive ÷ (read share + write share × penalty). Eight 15K drives at 70% reads give about 842 IOPS in RAID 5 and 1,231 in RAID 10. For SSDs, whose writes are slower than reads, the calculator counts reads and writes separately.
How do I convert IOPS to MB/s?
MB/s = IOPS × block size. 10,000 IOPS at 4 KiB is 41 MB/s; the same 10,000 IOPS at 64 KiB is 655 MB/s. To go the other way, IOPS = MB/s ÷ block size. A drive reaches its peak IOPS at small blocks and its peak MB/s at large ones, so quote both with the block size.
How many IOPS does an SSD have?
Enterprise SATA SSDs are rated at about 75,000–98,000 random read and 25,000–30,000 write IOPS, 12 Gb/s SAS SSDs at 180,000–450,000 read and 60,000–90,000 write, and U.2 NVMe SSDs at 400,000 to about 1,000,000 read and 80,000–180,000 write. Datasheet figures are measured at deep queues; sustained mixed workloads run lower. The calculator uses the low end of each range.
What is a good IOPS number?
It depends on the workload. A small file server needs a few hundred IOPS, a general virtualization host about 50–100 IOPS per VM, and a busy OLTP database thousands to tens of thousands. Measure the current load where you can: Windows Performance Monitor (Disk Transfers/sec) or Linux iostat.
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 is how long one operation takes and decides how fast applications feel. Hard drives stream respectably but drop to double-digit IOPS on random work.
Does a RAID controller's cache increase IOPS?
Yes, for bursts. A battery- or flash-backed write-back cache confirms writes as soon as they reach the cache, which hides the parity write penalty for short peaks. Sustained random writes still reach the drives, so long-run IOPS settle near the calculator's figures.
How we calculate: write penalties follow the HPE Smart Array SR Gen10 user guide (RAID 0: 1, RAID 10: 2, RAID 5: 4, RAID 6: 6); hard-drive IOPS follow seek and rotational latency; SSD read and write IOPS and MB/s take the low end of current enterprise datasheets (Samsung PM893, PM1643a, PM9A3, Micron 5400 and 7450). Larger blocks add transfer time on hard drives and are capped by MB/s on SSDs. Estimates, not a guarantee: controller cache, queue depth and firmware change real results. Checked October 2026.