This page describes the service tiers that Filestore offers and provides guidance on selecting the tier that best suits your needs.
Overview
Filestore offers the following service tiers:
- Zonal
- Regional
- Basic HDD
Basic SSD
Each tier offers different capacity options and performance levels to fit different use cases. The following table shows a comparison of the tiers:
Service tier | Provisionable capacity | Scalability | Performance | Availability | Data protection |
---|---|---|---|---|---|
Zonal | 1 TiB to 9.75 TiB | Up or down in 256 GiB units | Configurable | Zonal | Backups, Snapshots |
Zonal | 10 TiB to 100 TiB | Up or down in 2.5 TiB units | Configurable | Zonal | Backups, Snapshots |
Regional | 1 TiB to 9.75 TiB | Up or down in 256 GiB units | Configurable | Regional | Backups, Snapshots |
Regional | 10 TiB to 100 TiB | Up or down in 2.5 TiB units | Configurable | Regional | Backups, Snapshots |
Enterprise | 1 TiB to 10 TiB | Up or down in 256 GiB units | Scales with capacity | Regional | Backups, Snapshots |
Basic HDD (on GKE)* | 100 GiB to 63.9 TiB | Up only in 1 GiB units | Standard fixed | Zonal | Backups |
Basic HDD | 1 TiB to 63.9 TiB | Up only in 1 GiB units | Standard fixed | Zonal | Backups |
Basic SSD | 2.5 TiB to 63.9 TiB | Up only in 1 GiB units | Premium fixed | Zonal | Backups |
* Basic HDD (on GKE) refers to basic HDD instances with a minimum capacity of 100 GiB provisioned with the Filestore CSI driver. Basic HDD (on GKE) instances with capacity lower than 1 TiB consume 1 TiB of quota.
Pricing
For detailed information about pricing for each service tier, see the Pricing page.
Zonal
The zonal (10 TiB to 100 TiB) service tier replaces the high scale SSD, a former service tier. This service tier is suitable for high performance computing application requirements such as genome sequencing, and financial services trading analysis.
Zonal instance capacity ranges from 1 TiB to 100 TiB:
- The zonal (1 TiB to 9.75 TiB) service tier with lower capacity range scales up or down in increments of 256 GiB (0.25 TiB). This tier is suitable for you if you require higher availability and lower capacity.
- The zonal (10 TiB to 100 TiB) service tier with higher capacity range scales up or down in increments of 2.5 TiB. This tier is a more cost-effective option compared to the regional service tier.
Zonal instances allow for non-disruptive upgrades (NDUs) and support custom performance that lets you define the performance settings independently from capacity.
For detailed specifications, see the following table:
Specification | Zonal (1 TiB to 9.75 TiB) | Zonal (10 TiB to 100 TiB) |
---|---|---|
Client connections | 2,000 per 1 TiB, scaling in increments of 500, for up to 19,500 connections |
8,000 per 10 TiB, scaling in increments of 2,000, for up to 80,000 connections |
File size | Up to the size of the instance capacity | Up to the size of the instance capacity |
Number of files* | Approximately 89,000,000 files per 1 TiB of capacity | Approximately 89,000,000 files per 1 TiB of capacity |
File locks | 250 per file | 250 per file |
Minimum capacity | 1 TiB | 10 TiB |
Maximum capacity | 9.75 TiB | 100 TiB |
Scaling direction | Up or down | Up or down |
Minimum scaling units | 256 GiB | 2.5 TiB |
Read throughput | 260 MiB/s per 1 TiB of provisioned capacity | 650 MiB/s per 2.5 TiBs of provisioned capacity |
Write throughput | 88 MiB/s per 1 TiB of provisioned capacity | 220 MiB/s per 2.5 TiBs of provisioned capacity |
Read IOPS | 9,200 per 1 TiB of provisioned capacity | 23,000 per 2.5 TiBs of provisioned capacity |
Write IOPS | 2,600 per 1 TiB of provisioned capacity | 6,500 per 2.5 TiBs of provisioned capacity |
Availability | Zonal | Zonal |
Data protection | Backups, Snapshots | Backups, Snapshots |
Customer-managed encryption keys | Supported | Supported |
Non-disruptive maintenance | Supported (zonal instances remain available during maintenance events.) | Supported (zonal instances remain available during maintenance events.) |
Google Cloud VMware Engine | Supported | Supported |
Filestore multishares for GKE | Not supported | Not supported |
Protocol support | NFSv3, NFSv4.1 | NFSv3, NFSv4.1 |
Instance replication | Supported (Allowlisted GA) | Supported (Allowlisted GA) |
Custom performance | Supported | Supported |
* The number of files listed is an indication of the maximum number of supported connections to small or empty files. The number of supported file connections decreases as file size increases. While no practical limit exists across service tiers, instance performance may be delayed when supporting a large number of files.
Zonal limitations
Capacity range selection is permanent. Once the outer limits of the instance capacity are met, the service tier doesn't scale up or down to a new capacity range. If greater or lower capacity is needed, you must create a new instance with the service tier and capacity range you want to use.
Regional
Regional service tier is intended for applications requiring continuous availability and regional resilience.
Regional instance capacity ranges from 1 TiB to 100 TiB:
- The regional (1 TiB to 9.75 TiB) service tier with lower capacity range scales up or down in increments of 256 GiB (0.25 TiB).
- The regional (10 TiB to 100 TiB) service tier with higher capacity range scales up or down in increments of 2.5 TiB.
Regional provides the following benefits:
- Optimized for enterprise-grade network attached storage (NAS)
- Provides regional storage resilient to zone outages which supports the following:
- Data replication across multiple zones within a region
- High availability for mission-critical, high performance computing workloads running within a large namespace
- Allows for non-disruptive upgrades (NDUs)
- Offers linear performance that changes with capacity, staying within the stated capacity range.
- Supports custom performance, letting you set performance options separately from capacity.
For detailed specifications, see the following table:
Specification | Regional (1 TiB to 9.75 TiB) | Regional (10 TiB to 100 TiB) |
---|---|---|
Client connections | 2,000 per 1 TiB, scaling in increments of 500, for up to 19,500 connections |
8,000 per 10 TiB, scaling in increments of 2,000, for up to 80,000 connections |
File size | Up to the size of instance capacity | Up to the size of instance capacity |
Number of files* | Approximately 89,000,000 files per 1 TiB of capacity | Approximately 89,000,000 files per 1 TiB of capacity |
File locks | 250 per file | 250 per file |
Performance | Configurable | Configurable |
Minimum capacity | 1 TiB | 10 TiB |
Maximum capacity | 9.75 TiB | 100 TiB |
Scaling direction | Up or down | Up or down |
Minimum scaling units | 256 GiB | 2.5 TiB |
Read throughput | 120 MiB/s per 1 TiB of provisioned capacity | 650 MiB/s per 2.5 TiBs of provisioned capacity |
Write throughput | 100 MiB/s per 1 TiB of provisioned capacity | 220 MiB/s per 2.5 TiBs of provisioned capacity |
Read IOPS | 12,000 per 1 TiB of provisioned capacity | 23,000 per 2.5 TiBs of provisioned capacity |
Write IOPS | 4,000 per 1 TiB of provisioned capacity | 6,500 per 2.5 TiBs of provisioned capacity |
Availability | Regional | Regional |
Data protection | Backups, Snapshots |
Backups, Snapshots |
Customer-managed encryption keys | Supported | Supported |
Non-disruptive maintenance | Supported (Regional instances remain available during maintenance events.) | Supported (Regional instances remain available during maintenance events.) |
Google Cloud VMware Engine | Supported | Supported |
Filestore multishares for GKE | Not supported | Not supported |
Protocol support | NFSv3, NFSv4.1 | NFSv3, NFSv4.1 |
Instance replication | Supported (Allowlisted GA) | Supported (Allowlisted GA) |
Custom performance | Supported | Supported |
* The number of files listed is an indication of the maximum number of supported connections to small or empty files. The number of supported file connections decreases as file size increases. While no practical limit exists across service tiers, instance performance may be delayed when supporting a large number of files.
Regional limitations
The following limitations apply:
The regional service tier can't be combined with the Filestore multishares feature.
The regional service tier can't be combined with the GKE Filestore CSI driver.
10 TiB regional instances must be created with the higher capacity range specification (10 TiB to 100 TiB).
The same limitations that apply to enterprise backups also apply to regional backups.
Backup
restore
operations are only supported when restoring to a new instance. For these operations, the new instance must match the service tier and also accommodate instance capacity greater than or equal to the size of the backup.For a detailed description of backup limitations, see Backups.
While performance scales linearly with capacity, note that a 10 TiB enterprise instance will have better performance than a 10 TiB regional instance.
Performance scales linearly with capacity within the parameters of the specified capacity range. Performance is not linear between the two regional capacity ranges. A regional instance with 9.75 TiB of capacity will have better performance, for example, with an upper limit of 117,000 Read IOPS, than a regional instance with 10 TiB of instance capacity, with an upper limit of 92,000 Read IOPS. For more information, see Performance.
Capacity range selection is permanent. Once the outer limits of the instance capacity are met, the service tier does not scale up or down to a new capacity range. If greater or lower capacity is needed, you must create a new instance with the service tier and capacity range you want to use.
Enterprise
You can use the enterprise service tier if you need a Filestore instance with multishares or if you want to use the Filestore CSI driver to create and manage instances. For any other use cases, use regional service tier.
A Filestore enterprise instance combined with the Filestore multishares for GKE feature supports up to 80 shares in the instance.
For detailed specifications, see the following table:
Specification | Enterprise |
---|---|
Client connections | 2,000 per 1 TiB, scaling in increments of 500, for up to 20,000 connections |
File size | Up to the size of instance capacity |
Number of files* | Approximately 89,000,000 files per 1 TiB of capacity |
File locks | 250 per file |
Minimum capacity | 1 TiB |
Maximum capacity | 10 TiB |
Scaling direction | Up or down |
Minimum scaling units | 256 GiB |
Read throughput | 120 MiB/s per 1 TiB of provisioned capacity |
Write throughput | 100 MiB/s per 1 TiB of provisioned capacity |
Read IOPS | 12,000 per 1 TiB of provisioned capacity |
Write IOPS | 4,000 per 1 TiB of provisioned capacity |
Availability | Regional |
Data protection | Backups, Snapshots |
Customer-managed encryption keys | Supported |
Non-disruptive maintenance | Supported (Enterprise instances remain available during maintenance events.) |
Google Cloud VMware Engine | Supported |
Filestore multishares for GKE | Supported |
Protocol support | NFSv3, NFSv4.1 | NFSv3, NFSv4.1 |
Instance replication | Supported (Allowlisted GA) | Supported (Allowlisted GA) |
* The number of files listed is an indication of the maximum number of supported connections to small or empty files. The number of supported file connections decreases as file size increases. While no practical limit exists across service tiers, instance performance may be delayed when supporting a large number of files.
Basic HDD and basic SSD
Basic-tier Filestore instances are suitable for file sharing, software development, and use with GKE workloads. You can choose either HDD or SSD for storing data, with SSD offering greater performance at a higher cost.
Basic HDD instances have a performance increase when the provisioned capacity exceeds 10 TiB. The performance of basic SSD instances is fixed regardless of the provisioned capacity.
For detailed specifications, see the following table:
Specification | Basic HDD | Basic SSD |
---|---|---|
Client connections | Recommended limit of 500 | Recommended limit of 500 |
File size | Up to 16 TiB | Up to 16 TiB |
Number of files* | 67,108,864 files per 1 TiB of capacity | 67,108,864 files per 1 TiB of capacity |
File locks | 128 per Filestore instance | 128 per Filestore instance |
Performance | Standard fixed | Premium fixed |
Minimum capacity |
|
2.5 TiB |
Maximum capacity | 63.9 TiB | 63.9 TiB |
Scaling direction | Up only | Up only |
Minimum scaling units | 1 GiB | 1 GiB |
Read throughput |
|
1,200 MiB/s |
Write throughput |
|
350 MiB/s |
Read IOPS |
|
60,000 |
Write IOPS |
|
25,000 |
Availability | Zonal | Zonal |
Data protection | Backups | Backups |
Customer-managed encryption keys | Not supported | Not supported |
Non-disruptive maintenance | Not supported | Not supported |
Google Cloud VMware Engine | Not supported | Not supported |
Filestore multishares for GKE | Not supported | Not supported |
Protocol support | NFSv3 | NFSv3 |
* The number of files listed is an indication of the maximum number of supported connections to small or empty files. The number of supported file connections decreases as file size increases. While no practical limit exists across service tiers, instance performance may be delayed when supporting a large number of files.
† Basic HDD (on GKE) refers to basic HDD instances with a minimum capacity of 100 GiB provisioned with the Filestore CSI driver. Basic HDD instances with capacity lower than 1 TiB consume 1 TiB of quota.
Former Filestore service tiers
Filestore former service tiers include the following:
- Standard
- Premium
- High scale SSD
These service tiers have the following replacements:
- Basic HDD replaces the standard service tier.
- Basic SSD replaces the premium service tier.
- Zonal (10 TiB to 100 TiB) replaces the high scale SSD service tier.
When creating new instances, use basic , zonal, and regional service tiers. You can't create instances from the former service tiers using Google Cloud console. Instead, use Filestore API or Google Cloud CLI.
Quota
A Filestore project's storage capacity and instance quota are influenced by the region and service tier you choose.
Zonal quota comparison
The following quotas apply to zonal instances:
- Zonal (1 TiB to 9.75 TiB) offers the same per project, per region, instance quota as the regional and enterprise service tiers.
- Zonal (10 TiB to 100 TiB) offers the same per project, region, and instance quota as the high scale SSD service tier.
Regional quota comparison
The following quotas apply to regional instances:
- Regional (1 TiB to 9.75 TiB) offers the same per project, region, and instance quota as the enterprise service tier.
- Regional (10 TiB to 100 TiB) offers the same per project, region, and instance quota as the high scale SSD service tier.
To see your available quota, go to the Quotas & Limits page in the Google Cloud console.
If you need to request additional quota, see Requesting quota increases.
What's next
- Get started using Filestore by installing and enabling Filestore components.
- Learn more about Filestore in the technical overview.
- See the regions that support Filestore.
- Learn more about Filestore multishares for GKE.
- Learn more about Limits.