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:
- Basic HDD
- Basic SSD
- Zonal with a lower capacity range
- Zonal with a higher capacity range (previously high scale SSD)
- Enterprise
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 | Monthly pricing* |
---|---|---|---|---|---|---|
Basic HDD | 1 TiB to 63.9 TiB | Up only in 1 GiB units | Standard fixed | Zonal | Backups | $163.84 ($0.16/GiB) |
Basic SSD | 2.5 TiB to 63.9 TiB | Up only in 1 GiB units | Premium fixed | Zonal | Backups | $768.00 ($0.30/GiB) |
Zonal, lower capacity range | 1 TiB to 9.75 TiB | Up or down in 256 GiB units | Scales with capacity | Zonal | Backups, Snapshots |
$256.00 ($0.25/GiB) |
Zonal, higher capacity range | 10 TiB to 100 TiB | Up or down in 2.5 TiB units | Scales with capacity | Zonal | Backups, Snapshots |
$2560.00 ($0.25/GiB) |
Enterprise | 1 TiB to 10 TiB | Up or down in 256 GiB units | Scales with capacity | Regional | Backups, Snapshots |
$460.80 ($0.45/GiB) |
* Reflects the estimated pricing for a Filestore instance with
minimum capacity and located in region us-central1
. For more information about
pricing, see the Pricing page.
Basic HDD and basic SSD tiers
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.
Specifications
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 |
Minimum capacity | 1 TiB | 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 |
Zonal
Filestore offers a zonal service tier with options for a higher or lower capacity range (GA). The entire service tier ranges from 1 TiB to 100 TiB in size.
Zonal with a higher capacity range
The zonal service tier with a higher capacity range replaces the previously available high scale SSD service tier. Instance capacity continues to range from 10 TiB to 100 TiB in size, and scale in increments of 2.5 TiB.
This offering is suitable for high performance computing application requirements such as genome sequencing, and financial-services trading analysis. It offers fast performance that scales up or down with capacity.
This service tier and capacity range offer the same quota as the legacy high scale SSD service tier.
Zonal with a lower capacity range
The zonal service tier with a lower capacity range provides similar performance with the following benefits:
Optional smaller capacity, with instances ranging from 1 TiB to 9.75 TiB in size
Support for scalability in increments of 256 GiB
Support for non-disruptive upgrades (NDUs)
When compared with basic SSD instances, zonal instances with the lower capacity range may provide a better option for users that require higher availability and lower capacity.
When compared with enterprise instances, it may provide a more cost-effective option.
If not specified, the lower capacity range is the default setting at instance creation.
This service tier and capacity range offers a quota that matches enterprise instances.
Zonal limitations
The following feature limits apply:
When pricing is implemented, applicable fees apply.
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.
Specifications
Specification | Zonal with a lower capacity range | Zonal with a higher capacity range |
---|---|---|
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 | No practical limit | No practical limit |
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 |
High scale SSD
High scale SSD is a legacy Filestore service tier.
Should you use high scale SSD?
When creating new instances, users are strongly encouraged to use the zonal service tier for their zonal file storage needs. The legacy high scale SSD service tier will continue to be supported for specific use cases such as users requiring backups for existing high scale SSD instances.
Enterprise tier
Enterprise instances are designed for enterprise-grade network file system (NFS) workloads, critical applications such as SAP, and GKE workloads. It supports regional high availability and data replication over multiple zones for resilience within a region.
Specifications
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 | No practical limit |
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 |
Enterprise tier with Filestore multishares for GKE
A Filestore enterprise tier instance combined with the Filestore multishares for GKE feature supports up to 80 shares in the instance.
For more information, see Filestore multishares for GKE.
Quota
A Filestore project's storage capacity and instance quota are influenced by the region and service tier you choose.
To see your available quota, go to the Quotas 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.