# Filestore adopts Colossus and separates IOPS from capacity > Google Cloud’s Filestore backend update separates performance from capacity, giving teams a new sizing choice for shared NFS storage on GKE. Canonical URL: https://www.devobs.io/news/news-google-cloud-filestore-colossus-backend/ By: Finn Larson Published: 2026-09-06T11:58:54.635Z Updated: 2026-09-06T11:58:54.635Z Event date: 2026-08-05 Section: Infrastructure Google Cloud announced a Colossus-based storage backend for Filestore on August 5, separating provisioned IOPS from storage capacity. The [Filestore announcement](https://cloud.google.com/blog/products/storage-data-transfer/filestore-file-service-runs-on-colossus?e=48754805) describes the change for its managed NFS service and highlights integration with Google Kubernetes Engine through the Filestore CSI driver. ## A different sizing decision The important product change is that teams can adjust performance without treating additional stored bytes as the only route to more I/O capacity. Google also describes smaller shared allocations through Filestore multishares for GKE. Those are service capabilities; they do not establish that any particular application will run faster after migration. For platform engineers, the useful question becomes which resource is limiting a shared filesystem. A repository workspace with many small file operations can behave differently from a workload streaming a few large files, even when their storage footprints match. Capacity, operation rate, throughput, and client concurrency deserve separate measurements. ## Check the application contract A pilot should replay representative file creation, metadata lookup, and update patterns with several clients active. Include lock contention and recovery after a client disappears, rather than measuring only sequential throughput. An NFS mount does not make a multi-file application update transactional. Teams should also map which identities and network paths can reach each share. Smaller allocations can improve organizational separation, but filesystem permissions and application authorization still need deliberate ownership. The practical next step is to record the current workload’s IOPS and capacity requirements independently, then test a matching Filestore configuration. That produces a defensible migration decision without turning the backend architecture announcement into an assumed performance result. ## Source references -