Compute Engine offers several types of storage options for your instances. Each of the following storage options has unique price and performance characteristics:
- Zonal persistent disk: Efficient, reliable block storage.
- Regional persistent disk: Regional block storage replicated in two zones.
- Local SSD: High performance, transient, local block storage.
- Cloud Storage buckets: Affordable object storage.
- Filestore: High performance file storage for Google Cloud users.
If you are not sure which option to use, the most common solution is to add a persistent disk to your instance.
By default, each Compute Engine instance has a single boot persistent disk (PD) that contains the operating system. When your apps require additional storage space, you can add one or more additional storage options to your instance. For cost comparisons, see disk pricing.
|Local SSDs||Cloud Storage buckets|
|Storage type||Efficient and reliable block storage||Efficient and reliable block storage with synchronous replication across two zones in a region||Cost-effective and reliable block storage||Cost-effective and reliable block storage with synchronous replication across two zones in a region||Fast and reliable block storage||Fast and reliable block storage with synchronous replication across two zones in a region||Highest performance persistent block storage option||High performance local block storage||Affordable object storage|
|Minimum capacity per disk||10 GB||200 GB||10 GB||10 GB||10 GB||10 GB||500 GB||375 GB||n/a|
|Maximum capacity per disk||64 TB||64 TB||64 TB||64 TB||64 TB||64 TB||64 TB||375 GB||n/a|
|Capacity increment||1 GB||1 GB||1 GB||1 GB||1 GB||1 GB||1 GB||375 GB||n/a|
|Maximum capacity per instance||257 TB*||257 TB*||257 TB*||257 TB*||257 TB*||257 TB*||257 TB*||9 TB||Almost infinite|
|Scope of access||Zone||Zone||Zone||Zone||Zone||Zone||Zone||Instance||Global|
|Data redundancy||Zonal||Multi-zonal||Zonal||Multi-zonal||Zonal||Multi-zonal||Zonal||None||Regional, dual-regional or multi-regional|
|Encryption at rest||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes||Yes|
|Custom encryption keys||Yes||Yes||Yes||Yes||Yes||Yes||Yes||No||Yes|
|How-to||Add a standard persistent disk||Add a regional standard persistent disk||Add a balanced persistent disk||Add a regional balanced persistent disk||Add an SSD persistent disk||Add a regional SSD persistent disk||Add an extreme persistent disk||Add a local SSD||Connect a bucket|
In addition to the storage options that Google Cloud provides, you can deploy alternative storage solutions on your instances.
- Create a file server or distributed file system on Compute Engine to use as a network file system with NFSv3 and SMB3 capabilities.
- Mount a RAM disk within instance memory to create a block storage volume with high throughput and low latency.
Block storage resources have different performance characteristics. Consider your storage size and performance requirements to help you determine the correct block storage type for your instances.
|Local SSD (SCSI)||Local SSD (NVMe)|
|Maximum sustained IOPS|
|Read IOPS per GB||0.75||0.75||6||6||30||30||–||–||–|
|Write IOPS per GB||1.5||1.5||6||6||30||30||–||–||–|
|Read IOPS per instance||7,500*||7,500*||15,000–80,000*||15,000–60,000*||15,000–100,000*||15,000–60,000*||15,000–120,000*||900,000||2,400,000|
|Write IOPS per instance||15,000*||15,000*||15,000–80,000*||15,000–30,000*||15,000–100,000*||15,000–30,000*||15,000–120,000*||800,000||1,200,000|
|Maximum sustained throughput (MB/s)|
|Read throughput per GB||0.12||0.12||0.28||0.28||0.48||0.48||–||–||–|
|Write throughput per GB||0.12||0.12||0.28||0.28||0.48||0.48||–||–||–|
|Read throughput per instance||240–1,200*||240–1,200*||240–1,200*||240–1,200*||240–1,200*||240–1,200*||240–2,200**||9,360||9,360|
|Write throughput per instance||76–400**||38–200**||240–1,200*||120–600*||240–1,200*||120–600*||240–2,200**||4,680||4,680|
Persistent disks created in multi-writer mode have specific IOPS and throughput limits. See performance of persistent disks in multi-writer mode for details.
Persistent disks are durable network storage devices that your instances can access like physical disks in a desktop or a server. The data on each persistent disk is distributed across several physical disks. Compute Engine manages the physical disks and the data distribution for you to ensure redundancy and optimal performance.
Persistent disks are located independently from your virtual machine (VM) instances, so you can detach or move persistent disks to keep your data even after you delete your instances. Persistent disk performance scales automatically with size, so you can resize your existing persistent disks or add more persistent disks to an instance to meet your performance and storage space requirements.
Add a persistent disk to your instance when you need reliable and affordable storage with consistent performance characteristics.
When you configure a persistent disk, you can select one of the following disk types.
- Standard persistent disks (
pd-standard) are backed by standard hard disk drives (HDD).
- Balanced persistent disks (
pd-balanced) are backed by solid-state drives (SSD). They are an alternative to SSD persistent disks that balance performance and cost.
- SSD persistent disks (
pd-ssd) are backed by solid-state drives (SSD).
- Extreme persistent disks (
pd-extreme) are backed by solid-state drives (SSD). With consistently high performance for both random access workloads and bulk throughput, extreme persistent disks are designed for high-end database workloads. Unlike other disk types, you can provision your desired IOPS. For more information, see Extreme persistent disks.
If you create a disk in the Cloud Console, the default disk type is
pd-balanced. If you create a disk using the
gcloud tool or the
Compute Engine API, the default disk type is
The following table shows disk type and machine type support for zonal persistent disks.
|Disk type||Supported machine types|
||All machine types|
||All machine types|
||All machine types|
||n2-standard with 64 or more vCPUs, m1-megamem-96, m2-ultramem-208, m2-ultramem-416|
The following table shows disk type and machine type support for regional persistent disks:
|Disk type||Supported machine types|
||N1, N2, N2D, E2|
||N1, N2, N2D, E2|
||N1, N2, N2D, E2|
Disk durability represents the probability of data loss, by design, for a typical disk in a typical year, using a set of assumptions about hardware failures, the likelihood of catastrophic events, isolation practices and engineering processes in Google data centers, and the internal encodings used by each disk type. Persistent disk data loss events are extremely rare and have historically been the result of coordinated hardware failures, software bugs, or a combination of the two. Google also takes many steps to mitigate the industry-wide risk of silent data corruption. Human error by a Google Cloud customer, such as when a customer accidentally deletes a disk, is outside the scope of persistent disk durability.
There is a very small risk of data loss occurring with a regional persistent disk due to its internal data encodings and replication. Regional persistent disks provide twice as many replicas as zonal persistent disks, with their replicas distributed between two zones in the same region, so they provide high availability and can be used for disaster recovery if an entire data center is lost and cannot be recovered (although that has never happened). The additional replicas in a second zone can be accessed immediately if a primary zone becomes unavailable during a long outage.
Note that durability is in the aggregate for each disk type, and does not represent a financially-backed service level agreement (SLA).
The table below shows durability for each disk type's design. 99.999% durability means that with 1,000 disks, you would likely go a hundred years without losing a single one.
|Zonal standard persistent disk||Zonal balanced persistent disk||Zonal SSD persistent disk||Zonal extreme persistent disk||Regional standard persistent disk||Regional balanced persistent disk||Regional SSD persistent disk|
|Better than 99.99%||Better than 99.999%||Better than 99.999%||Better than 99.9999%||Better than 99.999%||Better than 99.9999%||Better than 99.9999%|
Zonal persistent disks
Ease of use
Compute Engine handles most disk management tasks for you so that you do not need to deal with partitioning, redundant disk arrays, or subvolume management. Generally, you don't need to create larger logical volumes, but you can extend your secondary attached persistent disk capacity to 257 TB per instance and apply these practices to your persistent disks if you want. You can save time and get the best performance if you format your persistent disks with a single file system and no partition tables.
If you need to separate your data into multiple unique volumes, create additional disks rather than dividing your existing disks into multiple partitions.
Persistent disk performance is predictable and scales linearly with provisioned capacity until the limits for an instance's provisioned vCPUs are reached. For more information about performance scaling limits and optimization, see Block storage performance.
Standard persistent disks are efficient and economical for handling sequential read/write operations, but they aren't optimized to handle high rates of random input/output operations per second (IOPS). If your apps require high rates of random IOPS, use SSD or extreme persistent disks. SSD persistent disks are designed for single-digit millisecond latencies. Observed latency is application specific.
Compute Engine optimizes performance and scaling on persistent disks automatically. You don't need to stripe multiple disks together or pre-warm disks to get the best performance. When you need more disk space or better performance, resize your disks and possibly add more vCPUs to add more storage space, throughput, and IOPS. Persistent disk performance is based on the total persistent disk capacity attached to an instance and the number of vCPUs that the instance has.
For boot devices, you can reduce costs by using a standard persistent disk. Small, 10 GB persistent disks can work for basic boot and package management use cases. However, to ensure consistent performance for more general use of the boot device, use a balanced persistent disk as your boot disk.
Each persistent disk write operation contributes to the cumulative network egress traffic for your instance. This means that persistent disk write operations are capped by the network egress cap for your instance.
Persistent disks have built-in redundancy to protect your data against equipment failure and to ensure data availability through datacenter maintenance events. Checksums are calculated for all persistent disk operations, so we can ensure that what you read is what you wrote.
Additionally, you can create snapshots of persistent disks to protect against data loss due to user error. Snapshots are incremental, and take only minutes to create even if you snapshot disks that are attached to running instances.
You can attach an SSD persistent disk in multi-writer mode to up to two N2 VMs simultaneously so that both VMs can read and write to the disk. Persistent disks in multi-writer mode provide a shared block storage capability and present an infrastructural foundation for building distributed Network File System (NFS) and similar highly available services. However, persistent disks with multi-writer mode require specialized file systems such as GlusterFS or GFS2. Many file systems such as EXT4, XFS, and NTFS are not designed to be used with shared block storage. For more information about the best practices when sharing persistent disks between VMs, see Best practices. If you require a fully managed file storage, you can mount a Filestore file share on your Compute Engine VMs.
To enable multi-writer mode for new persistent disks, create a new persistent
disk and specify the
--multi-writer flag in the
gcloud tool or the
multiWriter property in the Compute Engine API. For more information, see
Sharing persistent disks between VMs.
Persistent disk encryption
Compute Engine automatically encrypts your data before it travels outside of your instance to persistent disk storage space. Each persistent disk remains encrypted either with system-defined keys or with customer-supplied keys. Google distributes persistent disk data across multiple physical disks in a manner that users do not control.
When you delete a persistent disk, Google discards the cipher keys, rendering the data irretrievable. This process is irreversible.
If you want to control the encryption keys that are used to encrypt your data, create your disks with your own encryption keys.
You cannot attach a persistent disk to an instance in another project.
You can attach a balanced persistent disk to at most 10 VM instances in read-only mode.
Each persistent disk can be up to 64 TB in size, so there is no need to manage arrays of disks to create large logical volumes. Each instance can attach only a limited amount of total persistent disk space and a limited number of individual persistent disks. Predefined machine types and custom machine types have the same persistent disk limits.
Most instances can have up to 128 persistent disks and up to 257 TB of total persistent disk space attached. Total persistent disk space for an instance includes the size of the boot persistent disk.
Shared-core machine types are limited to 16 persistent disks and 3 TB of total persistent disk space.
Creating logical volumes larger than 64 TB might require special consideration. For more information see larger logical volume performance.
Regional persistent disks
Regional persistent disks have storage qualities that are similar to zonal persistent disks. However, regional persistent disks provide durable storage and replication of data between two zones in the same region.
If you are designing robust systems or high availability services on Compute Engine, use regional persistent disks combined with other best practices such as backing up your data using snapshots. Regional persistent disks are also designed to work with regional managed instance groups.
In the unlikely event of a zonal outage, you can usually failover your workload
running on regional persistent disks to another zone by using the
--force-attach flag lets you attach the regional persistent disk to
a standby VM instance even if the disk can't be detached from the original VM
due to its unavailability. To learn more, see Regional persistent disk
failover. You cannot force attach a zonal
persistent disk to an instance.
Regional persistent disks are an option when write performance is less critical than data redundancy across multiple zones.
Like zonal persistent disks, regional persistent disks can achieve greater IOPS and throughput performance on instances with a greater number of vCPUs. For more information about this and other limitations, see SSD persistent disk performance limits.
When you need more disk space or better performance, you can resize your regional disks to add more storage space, throughput, and IOPS.
Compute Engine replicates data of your regional persistent disk to the zones you selected when you created your disks. The data of each replica is spread across multiple physical machines within the zone to ensure redundancy.
Similar to zonal persistent disks, you can create snapshots of persistent disks to protect against data loss due to user error. Snapshots are incremental, and take only minutes to create even if you snapshot disks that are attached to running instances.
- You can't use a regional persistent disk with a memory-optimized, compute-optimized, or accelerator-optimized machine type VM.
- You cannot use regional persistent disks as boot disks.
- You can create a regional persistent disk from a snapshot but not an image.
- The minimum size of a regional standard persistent disk is 200 GB.
- When resizing a regional persistent disk, you can only increase its size.
- Regional persistent disks perform differently from zonal persistent disks. For more information, see Block storage performance.
Local SSDs are physically attached to the server that hosts your VM instance. Local SSDs have higher throughput and lower latency than standard persistent disks or SSD persistent disks. The data that you store on a local SSD persists only until the instance is stopped or deleted. Each local SSD is 375 GB in size, but you can attach a maximum of 24 local SSD partitions for a total of 9 TB per instance.
Create an instance with Local SSDs when you need a fast scratch disk or cache and don't want to use instance memory.
Local SSDs are designed to offer very high IOPS and low latency. Unlike persistent disks, you must manage the striping on local SSDs yourself. Combine multiple local SSD partitions into a single logical volume to achieve the best local SSD performance per instance, or format local SSD partitions individually.
The following table provides an overview of local SSD capacity and estimated performance using NVMe. To reach maximum performance limits with an N1 machine type, use 32 or more vCPUs. To reach maximum performance limits on an N2 and N2D machine type, use 24 or more vCPUs.
Local SSD encryption
Compute Engine automatically encrypts your data when it is written to local SSD storage space. You can't use customer-supplied encryption keys with local SSDs.
Data persistence on Local SSDs
Please read Local SSD data persistence to learn what events preserve your Local SSD data and what events can cause your Local SSD data to be unrecoverable.
You can create an instance with 16 or 24 local SSD partitions for 6 TB or 9 TB of local SSD space, respectively. This is available on instances with N1, N2, N2D, and custom machine types. To reach the maximum IOPS limits, use a VM instance with 32 or more vCPUs.
Instances with shared-core machine types can't attach any local SSD partitions.
You can't attach Local SSDs to E2, N2A, T2D and M2 machine types.
Local SSDs and machine types
You can attach Local SSDs to most machine types available on Compute Engine, unless otherwise noted. However, there are constraints around how many local SSDs you can attach based on each machine type:
|N1 machine types||Number of local SSD partitions allowed per VM instance|
|All N1 machine types||1 to 8, 16, or 24|
|N2 machine types|
|Machine types with 2 to 10 vCPUs, inclusive||1, 2, 4, 8, 16, or 24|
|Machine types with 12 to 20 vCPUs, inclusive||2, 4, 8, 16, or 24|
|Machine types with 22 to 40 vCPUs, inclusive||4, 8, 16, or 24|
|Machine types with 42 to 80 vCPUs, inclusive||8, 16, or 24|
|N2D machine types|
|Machine types with 2 to 16 vCPUs, inclusive||1, 2, 4, 8, 16, or 24|
|Machine types with 32 or 48 vCPUs||2, 4, 8, 16, or 24|
|Machine types with 64 or 80 vCPUs||4, 8, 16, or 24|
|Machine types with 96 to 224 vCPUs, inclusive||8, 16, or 24|
|C2 machine types|
|Machine types with 4 or 8 vCPUs||1, 2, 4, or 8|
|Machine types with 16 vCPUs||2, 4, or 8|
|Machine types with 30 vCPUs||4 or 8|
|Machine types with 60 vCPUs||8|
|A2 machine types|
||1, 2, 4, or 8|
||2, 4, or 8|
||4 or 8|
|M1 machine types|
||1 to 8|
|E2, N2A, T2D and M2 machine types||These machine types don't support local SSD drives.|
Local SSDs and preemptible VM instances
You can start a preemptible VM instance with a local SSD and Compute Engine charges you discounted spot prices for the local SSD usage . Local SSDs attached to preemptible instances work like normal local SSDs, retain the same data persistence characteristics, and remain attached for the life of the instance.
Compute Engine doesn't charge you for local SSDs if their instances are preempted in the first minute after they start running.
For more information about local SSDs, see Adding local SSDs.
Reserving Local SSDs with committed use discounts
To reserve Local SSD resources in a specific zone, see Reserving zonal resources. Reservations are required for committed-use pricing for Local SSDs.
Cloud Storage buckets
Cloud Storage buckets are the most flexible, scalable, and durable storage option for your VM instances. If your apps don't require the lower latency of Persistent Disks and Local SSDs, you can store your data in a Cloud Storage bucket.
Connect your instance to a Cloud Storage bucket when latency and throughput aren't a priority and when you must share data easily between multiple instances or zones.
The performance of Cloud Storage buckets depends on the storage class that you select and the location of the bucket relative to your instance.
The standard storage class used in the same location as your instance gives performance that is comparable to persistent disks but with higher latency and less consistent throughput characteristics. The standard storage class used in a multiregional location stores your data redundantly across at least two regions within a larger multiregional location.
Nearline and coldline storage classes are primarily for long-term data archival. Unlike the standard storage class, these archival classes have minimum storage durations and read charges. Consequently, they are best for long-term storage of data that is accessed infrequently.
All Cloud Storage buckets have built-in redundancy to protect your data against equipment failure and to ensure data availability through datacenter maintenance events. Checksums are calculated for all Cloud Storage operations to help ensure that what you read is what you wrote.
Unlike persistent disks, Cloud Storage buckets aren't restricted to the zone where your instance is located. Additionally, you can read and write data to a bucket from multiple instances simultaneously. For example, you can configure instances in multiple zones to read and write data in the same bucket rather than replicate the data to persistent disks in multiple zones.
Furthermore, you can mount a Cloud Storage bucket to your instance as a file system. Mounted buckets function similarly to a persistent disk when you read or write files. However, Cloud Storage buckets are object stores that don't have the same write constraints as a POSIX file system and can't be used as boot disks. Your instance can write data to a file and overwrite critical data from other instances that are also writing data to the storage object simultaneously.
Cloud Storage encryption
Compute Engine automatically encrypts your data before it travels outside of your instance to Cloud Storage buckets. You don't need to encrypt files on your instances before you write them to a bucket.
Just like persistent disks, you can encrypt buckets with your own encryption keys.
- Add a persistent disk to your instance.
- Add a regional persistent disk to your instance.
- Create an instance with Local SSDs.
- Connect your instance to a Cloud Storage bucket.
- Create a file server or distributed file system.
- Review the quota limits for disks.
- Mount a RAM disk on your instance.
Try it for yourself
If you're new to Google Cloud, create an account to evaluate how Compute Engine performs in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.Try Compute Engine free