Oracle Cloud Infrastructure Documentation

Changing the Performance of a Volume

The Block Volume service enables you to dynamically configure the performance level for block volumes and boot volumes. For more information, see Block Volume Performance.

If you configure performance level for a block volume to the ultra high performance level the volume attachment should be multipath-enabled. You may need to take additional steps to optmize the volume's performance, for more information, see Attaching Ultra High Performance Volumes. This does not apply to boot volumes configured for the ultra high performance level.

Note

When you change a block volume's performance to ultra high performance from any other performance level you need to detach and then reattach the volume. See Detaching a Volume and Attaching a Block Volume to an Instance.

Required IAM Service Policy

To use Oracle Cloud Infrastructure, an administrator must be a member of a group granted security access in a policy  by a tenancy administrator. This access is required whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you get a message that you don't have permission or are unauthorized, verify with the tenancy administrator what type of access you have and which compartment  your access works in.

For administrators: The policy in Let volume admins manage block volumes, backups, and volume groups lets the specified group do everything with block volumes and backups, but not launch instances.

If you're new to policies, see Managing Identity Domains and Common Policies. For reference material about writing policies for instances, cloud networks, or other Core Services API resources, see Details for the Core Services.

Limitations

  • When you adjust the VPUs/GB setting for a volume, the volume's lifecycle state transitions to Provisioning while service updates the settings. During this process, you can't attach the volume to an instance or perform other volume operations. After this process is complete, the volume lifecycle state transitions back to Available. At this point, you can attach the volume to an instance.

  • You can only change the performance level on three volumes concurrently per tenancy.