Performance expectations

For information about Cloud Volumes Service benchmarks, see NetApp Cloud Volumes Service for Google Cloud: Benchmarks.

For information about Cloud Volumes Service performance, see Enterprise Applications on Google Cloud: An Introduction to Cloud Volumes Service For Google Cloud.

For information about service level and allocated capacity, see Selecting the service level and allocated capacity.

Understanding space provisioning for a volume

Because space provisioning for a volume affects its capacity and performance, you should provision the right amount of capacity with the right service level to achieve your performance objectives.

For example, a CVS-Performance volume with 5 TiB of provisioned space and the Extreme service level provides a throughput of 5 * 128 MiB/s.

For more information, see Selecting the appropriate service level and allocated capacity for NetApp Cloud Volumes Service.

A volume of the CVS-Performance service type always shows 100 TiBs, regardless of the actual provisioned size. You can store up to 100 TiB in the volume before encountering an “out of space” condition. This behavior does not apply to volumes of the CVS service type.

You can use the df command to monitor the free space of a volume.

You are charged for the provisioned space or the used space, whichever is greater. Examples:

  • If your volume has 2 TiB of provisioned space and you use only 1 TiB, then you are charged for 2 TiB.
  • If your volume has 2 TiB of provisioned space and you use 3 TiB, then you are charged for 3 TiB.

For more information about billing calculations, see Pricing.

If you store more data than the space provisioned for a volume, then you are charged for the used space, but the volume gets the performance for the provisioned space.