Calculate OCI Block Volume IOPS, throughput, and monthly costs by performance tier.
Last verified: May 2026
Output will appear here...Your team is provisioning storage for a new PostgreSQL database needing 20,000 IOPS sustained. Naive approach: AWS-style 'pick a high IOPS tier'. The calculator shows: 256 GB Higher Performance volume = $19/month + 19,200 IOPS (close, may bottleneck); 384 GB Higher Performance = $29/month + 25,000 IOPS. Better path: 320 GB Balanced volume = $7/month delivers 19,200 IOPS at the lowest tier. The team saves $264/year on each of 30 database volumes ($7,920 fleet savings).
OCI Block Volumes offer configurable performance tiers — Lower Cost, Balanced, and Higher Performance — with different IOPS and throughput limits per GB. Unlike AWS EBS where you choose from fixed volume types, OCI lets you select a performance level and the IOPS and throughput scale linearly with volume size within that tier. The Block Volume Calculator helps you determine the right volume size and performance tier combination to meet your IOPS and throughput requirements. It also calculates costs including any additional performance units purchased beyond the included baseline.
The calculator takes inputs (volume size, performance tier, expected workload IOPS/throughput needs) and computes: IOPS available at that size+tier, throughput available, monthly cost (per-GB rate × size + optional VPU/performance-units cost). It also models backup costs based on data change rate and retention policy.
OCI Block Volumes can change performance tier ONLINE without detaching — a feature AWS EBS doesn't support without volume modification + cooldown. Use this for cost optimization: run at Lower Cost tier most of the time, bump to Higher Performance during heavy batch processing, drop back when done.
Performance scales LINEARLY with volume size. A 256 GB Balanced volume gives 15,360 IOPS; a 512 GB Balanced volume gives 25,000 IOPS (capped). For IOPS-bound workloads, sometimes the cheapest path to more IOPS is just a bigger volume — not a higher-priced tier.
Backups are stored in Object Storage and billed separately. Incremental backups only store changes, but if your data churn rate is high, backup storage can exceed the volume cost. Lifecycle policies on backup retention (e.g., daily for 7 days, weekly for 30 days, monthly for 1 year) prevent runaway costs.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.