Block Volumes
Product |
Comparison price (/vCPU)* |
Unit price |
Unit |
Block Volume Storage1 |
Gigabyte storage capacity per month |
||
Block Volume Performance Units2 |
Performance Units per gigabyte per month
|
1 Usage is measured with the Gigabyte Storage Capacity Per Month metric, by calculating the total block volume storage consumed for each calendar month until the block volumes are deleted. At a minimum, users will be charged for 1 minute. For anything beyond 1 minute, usage is tracked per second and prorated based on the number of seconds in a month using the per Gigabyte Storage Capacity Per Month pricing.
2 Usage is measured with the Gigabyte Performance Units Per Month metric, by calculating the total block volume performance consumed for each calendar month until the block volumes are deleted. At a minimum, users will be charged for 1 minute. For anything beyond 1 minute, usage is tracked per second and prorated based on the number of seconds in a month using the per Gigabyte Storage Capacity Per Month pricing.
*To make it easier to compare pricing across cloud service providers, Oracle web pages show both vCPU (virtual CPUs) prices and OCPU (Oracle CPU) prices for products with compute-based pricing. The products themselves, provisioning in the portal, billing, etc. continue to use OCPU (Oracle CPU) units. OCPUs represent physical CPU cores. Most CPU architectures, including x86, execute two threads per physical core, so 1 OCPU is the equivalent of 2 vCPUs for x86-based compute. The per-hour OCPU rate customers are billed at is therefore twice the vCPU price since they receive two vCPUs of compute power for each OCPU, unless it's a sub-core instance such as preemptible instances.