Help Center> Cloud Container Engine> User Guide> User Guide for Autopilot Clusters> Storage> Scalable File Service> Overview
Updated on 2024-07-05 GMT+08:00
View PDF

Overview

Introduction

CCE Autopilot allows you to mount a volume that is created from a Scalable File Service (SFS) file system to a container for persistent data storage. SFS volumes are commonly used in ReadWriteMany scenarios for large-capacity expansion and cost-sensitive services, such as media processing, content management, big data analysis, and workload analysis. For services with a massive number of small files, SFS Turbo file systems are recommended.

Expandable to petabytes, SFS provides fully hosted shared file storage, highly available and stable to handle data- and bandwidth-intensive applications

  • Standard file protocols: You can mount file systems as volumes to servers, the same as using local directories.
  • Data sharing: The same file system can be mounted to multiple servers, so that data can be shared.
  • Private network: Users can access data only in private networks of data centers.
  • Capacity and performance: The capacity of a single file system is high (PB level) and the performance is excellent (ms-level read/write I/O latency).
  • Use cases: Deployments and StatefulSets in the ReadWriteMany mode, and jobs created for high-performance computing (HPC), media processing, content management, web services, big data analysis, and workload process analysis

Performance

CCE Autopilot supports SFS 3.0 file systems. For details about file system types, see File System Type.

Table 1 Performance

Parameter

SFS 3.0

Maximum bandwidth

1.25 TB/s

Maximum IOPS

Million

Latency

10 ms

Maximum capacity

EB

Application Scenarios

SFS supports the following mounting modes based on application scenarios:

  • Using an Existing File System Through a Static PV: static provisioning. You use an existing file system to create a PV and then mount the PV to the workload through a PVC. This mode applies to scenarios where the underlying storage is available or billed on a yearly/monthly basis.
  • Using an SFS File System Through a Dynamic PV: dynamic provisioning. You do not need to create volumes in advance. Instead, you need to specify a StorageClass during PVC creation. A file system and a PV will be automatically created. This mode applies to scenarios where no underlying storage is available.

Billing

  • For SFS volumes automatically created using StorageClass, the default billing mode is Pay-per-use. You are billed based on the storage capacity and duration. For SFS pricing details, see Billing.
  • If you want to be billed on a yearly/monthly basis, use existing SFS volumes.
Parent topic: Scalable File Service