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.
Cloud Volumes Service supports dynamic increase and decrease of volume size. A volume is provisioned to allow writing data up to its allocated capacity.
Snapshot space requirements
Cloud Volumes Service provides advanced snapshot capabilities. For details, see Creating and managing volume snapshots.
The logical used space in the volume is a combination of data in the active file system and deleted blocks retained by snapshots. Retained snapshot blocks are freed as soon as the last snapshot referencing the blocks is deleted.
You're charged for provisioned space. The logical space used—including any deleted data retained by snapshots—consumes provisioned space.
Space requirement example
A user provisions a 5 TiB volume and writes 3 TiB of data into the volume.
Result: The client sees 2 TiB of free space.
The client creates a snapshot and then deletes 1 TiB of data.
Result: The client still sees only 2 TiB of free space (5 TiB volume - 2 TiB user data - 1 TiB snapshot data). This is because the system needs to retain 1 TiB of deleted data that is referenced by the snapshot. That capacity is counted against the allocated capacity.
The snapshot is deleted.
Result: 1 TiB of snapshot data is freed, and the client sees 3 TiB of free space.
Billing for your volumes
You're charged for the provisioned (allocated) space.
For example, if your volume has 2 TiB of provisioned space and you use only 1 TiB, then you are charged for 2 TiB.
For more information about billing calculations, see Pricing.
Monitor provisioned space
NetApp recommends that you monitor the usage of your volumes so that you can select an appropriate allocated capacity for your volumes and choose a new size as needed. Allocate sufficient capacity to meet the needs of your application and to prevent your volumes from running out of space at full utilization. NetApp recommends maintaining a provisioned space buffer of 20% above your expected volume utilization.
Cloud Monitoring includes metrics for monitoring Cloud Volumes Service. The
volume_usage metric represents the actual usage of the volume, and
volume_size represents the allocated capacity of the volume.
You can view charts for individual metrics in Metrics Explorer, create a dashboard with multiple charts, add alerting, or retrieve metrics data with the Cloud Monitoring API.
For more information, see Monitoring cloud volumes.
View usage and allocated capacity in the Cloud Console
You can view the usage and provisioned space for volumes on the Volumes page in the Cloud Console.
In the Cloud Console, go to the Volumes page.
To show the Usage column, click Column display options at the top of the volumes list, and select Usage.
The monitoring that is closest to the application is from within the virtual machine on which the application is running. You can observe changes in behavior through capacity reporting from within the VM client operating system.
You can check the used and available capacity of a volume by using the client operating system features to query the network mapped drive properties:
Windows clients: Use the
dircommand at the command prompt, or use the Drive > Properties command in Windows Explorer.
Linux clients: Use the