IOPS Explained: Why Your Storage Feels Slow Even When It's Empty
A media company buys a storage array with 500,000 IOPS. Three editors open their 4K timelines. Playback sucked, frames dropped. The storage was 12% full.
IOPS (Input/Output Operations Per Second) is marketed like horsepower. But the number means nothing if your entire playback plumbing can’t sustain it.
Drives rated at 100,000 IOPS sound impressive. But your network switch has a different throughput, your workstation NIC throttles to 10 gigabits (and let’s not even get started on the CPU load from your video codec). You’ve got one hot water cylinder with six showers. When everyone turns on the tap at 7am, water runs at a trickle.
Databases need IOPS because they do millions of tiny reads and writes. Media workflows need sustained data rates. Storage must deliver 1.5GBps (big “B”) consistently while multiple editors work simultaneously. That’s not an IOPS challenge. That’s a solution design problem.
If you work backwards from the viewers eyes, you need to make sure nothing is going to choke video playback. Not the application, not the workstation’s CPU, not the infrastructure. And then you multiply the number of showers in your house.
Enterprise IT talks about IOPS. Media teams say “it feels slow.” They’re measuring different things. Theoretical capability versus user experience - under pressure, with a director breathing down their neck. You don’t need faster drives. You need to architect the entire path from storage to screen.
If a vendor shows you an IOPS number, ask: “How many simultaneous 4K ProRes 422 HQ streams can I play in real-time?” If they don’t answer you straight, their IOPS number is marketing. What if we stopped buying storage and started buying guarantees instead?
Read on our blog: https://skywrd.ai/iops-explained-why-your-storage-feels-slow-even-when-its-empty/