The Filestore Zonal tier is optimized for high performance computing (HPC), batch compute, and localized workloads that require high throughput and low latency. It lets you process large data sets, perform batch compute jobs, and advanced AI/ML training as well as build systems and development environments requiring fast local storage.
Zonal instances allow for non-disruptive upgrades (NDUs) and support custom performance that lets you define the performance settings independently from capacity.
The Zonal tier replaces the high scale SSD.
| Specification | Zonal (1 TiB to 9.75 TiB) | Zonal (10 TiB to 100 TiB) |
|---|---|---|
| Usage | Suitable for performance-critical workloads with low capacity needs | Suitable for performance-critical workloads with high capacity needs, very high number of connected clients, high single client throughput, or overall high IOPS or throughput |
| 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 (Restricted GA) | Supported (Restricted 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
The 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.