Calculateur IOPS Stockage vers MB/s Bande Passante
← Back to Main Calculator

IOPS to MB/s Bandwidth Calculator

Convert IOPS to throughput (MB/s, Gbps) or calculate required IOPS from target bandwidth for cloud storage planning.

% Read100%
39.06
MB/s
0.31
Gbps
3,000
at 64 KB block
1 GbE
0%
10 GbE
0%
25 GbE
0%
Block SizeMB/sMiB/sGbps

Formula Reference

Throughput (MB/s) =
(IOPS × Block KB) ÷ 1024
Bandwidth (Gbps) =
(MB/s × 8) ÷ 1000
Required IOPS =
(Target MB/s × 1024) ÷ Block KB
Storage Guide

IOPS to Throughput Calculator: Cloud Storage Performance Planning

Our IOPS to MB/s bandwidth calculator helps systems administrators and cloud architects convert between IOPS (Input/Output Operations Per Second), block size, and storage throughput (MB/s, MiB/s, Gbps). Whether you are provisioning AWS EBS gp3 volumes, Azure Premium SSDs, or GCP Hyperdisk, understanding the IOPS-throughput relationship is critical for cost-effective capacity planning. Use this calculator to determine whether your cloud volumes are IOPS-limited or bandwidth-limited for your specific workload.

The IOPS to MB/s Formula Explained

The fundamental relationship is: Throughput = IOPS × Block Size. Throughput (measured in MB/s or MiB/s) equals the number of I/O operations per second multiplied by the size of each operation. For example, 10,000 IOPS with 4 KB blocks yields 39.06 MB/s, while the same IOPS with 256 KB blocks yields 2,500 MB/s. This is why high-throughput workloads like video streaming use large block sizes while transaction-heavy OLTP databases use small blocks.

We include both decimal (MB/s = 1,000 KB/MB) and binary (MiB/s = 1,024 KiB/MiB) modes to match cloud provider billing units (decimal) versus operating system reporting (binary). AWS EBS and Azure Managed Disks bill in decimal GB, while tools like iostat and fio report in binary MiB/s. Our IOPS bandwidth calculator handles both, preventing costly provisioning mistakes.

Cloud Storage IOPS and Throughput Limits

Major cloud providers impose independent IOPS and throughput limits on their block storage volumes. AWS EBS gp3 offers a baseline of 3,000 IOPS and 125 MB/s, with provisionable maximums of 16,000 IOPS and 1,000 MB/s. Importantly, you cannot max out both simultaneously — the product of IOPS × block size is constrained by the throughput cap. For io2 Block Express volumes, AWS offers up to 256,000 IOPS and 4,000 MB/s, designed for the most demanding database workloads.

Azure Premium SSD v2 provides a baseline of 3,000 IOPS and 125 MB/s, scalable to 80,000 IOPS and 1,200 MB/s. GCP Hyperdisk Balanced offers up to 80,000 IOPS and 1,200 MB/s. The common pattern across platforms: each provisioned IOPS grants a certain throughput allowance, typically calculated on a 16 KB or 256 KB block basis depending on the volume type. Our IOPS converter profiles help you quickly determine which volume type matches your requirements.

The network bottleneck gauge in this calculator compares your calculated throughput against standard network link speeds (1 GbE, 10 GbE, 25 GbE). This is a critical check — even if your storage can deliver 2,000 MB/s, a single 10 GbE network interface caps out at approximately 1,250 MB/s (accounting for overhead). Cloud instances have instance-level bandwidth limits that may be lower than the attached volume's maximum throughput.

Standard Block Sizes by Workload

Choosing the correct block size for your IOPS to bandwidth conversion is essential for accurate planning. OLTP databases (MySQL, PostgreSQL, Oracle, SQL Server) typically use 4 KB to 16 KB blocks, matching database page sizes. Virtual machine file systems (VMFS, NTFS, ext4) commonly use 32 KB to 64 KB blocks. Media streaming and content delivery workloads use 256 KB to 1 MB blocks for sequential throughput. Log and journal writes are typically 4 KB to 8 KB synchronous operations.

AWS EBS bases its IOPS-to-throughput calculation on specific block sizes depending on volume type. For gp2 and gp3 volumes, the throughput limits are calculated using 16 KB I/O size. For io2 volumes, AWS uses 256 KB I/O size for throughput calculations. This means a gp3 volume at 16,000 IOPS with 4 KB blocks achieves only 62.5 MB/s before hitting the throughput cap, while the same IOPS with 256 KB blocks hits the 1,000 MB/s throughput limit first. Our comparison table shows throughput across all standard block sizes simultaneously.

For DevOps engineers and SREs, understanding the IOPS-to-bandwidth relationship is essential for right-sizing cloud infrastructure. Provisioning a volume with 64,000 IOPS but only 4 KB blocks yields only 250 MB/s — far below the volume's potential. Conversely, a volume with 3,000 IOPS using 1 MB blocks can theoretically achieve 3,000 MB/s, but will be throttled by the throughput cap. Use this IOPS bandwidth calculator to find the optimal balance between IOPS and throughput for your specific application needs and cloud budget.



Frequently Asked Questions

How do you convert IOPS to MB/s?

To convert IOPS to MB/s, use the formula: Throughput (MB/s) = (IOPS × Block Size in KB) ÷ 1024. For example, 10,000 IOPS with a 4 KB block size yields (10000 × 4) ÷ 1024 = 39.06 MB/s. With a 64 KB block size, the same 10,000 IOPS yields (10000 × 64) ÷ 1024 = 625 MB/s. Block size is the critical factor in the IOPS-to-bandwidth relationship.

What is the difference between IOPS and throughput?

IOPS (Input/Output Operations Per Second) measures the number of read/write operations a storage device can handle per second. Throughput (MB/s or Gbps) measures the actual data transfer rate. They are related by block size: Throughput = IOPS × Block Size. A drive with high IOPS but small block size may have low throughput, while a drive with moderate IOPS but large block size can have high throughput. Cloud storage services like AWS EBS cap both IOPS and throughput independently.

What block size should I use for IOPS calculations?

Common block sizes vary by workload: OLTP databases (MySQL, Oracle, SQL Server) typically use 4KB–16KB blocks; virtual machine disks (VMware, Hyper-V) use 32KB–64KB; video streaming and media workflows use 256KB–1MB; log writes use 4KB–8KB; and backup operations use 512KB–1MB. AWS EBS bases its IOPS limits on 16KB blocks for gp2/gp3 and 256KB for io2 volumes. Always match block size to your actual application I/O pattern.

What are the IOPS and throughput limits of AWS EBS gp3?

AWS EBS gp3 volumes have a baseline of 3,000 IOPS and 125 MB/s throughput for any volume size. You can provision up to 16,000 IOPS and 1,000 MB/s for an additional cost. IOPS and throughput are independent — you can max out IOPS at 16,000 with only 250 MB/s throughput, or max throughput at 1,000 MB/s with only 1,000 IOPS. This calculator helps you understand the relationship between these limits for capacity planning.

How do I calculate required IOPS for a target bandwidth?

To find required IOPS for a target bandwidth: IOPS = (Target MB/s × 1024) ÷ Block Size in KB. For 500 MB/s with 64 KB blocks: (500 × 1024) ÷ 64 = 8,000 IOPS. For 4 KB blocks: (500 × 1024) ÷ 4 = 128,000 IOPS. This reverse calculation is essential when provisioning cloud volumes to ensure both IOPS and throughput limits are adequate for your workload.