Apsara File Storage NAS (NAS) provides multiple types of file systems. You can select one or more types based on your workloads. This helps you ensure the reliability, security, and continuity of your workloads.
Business scenarios
General-purpose Performance NAS file systems are suitable for latency-sensitive file sharing workloads that require low latency, such as Linux or Windows applications for enterprises, container persistent volumes (PVs), web content management, and genetic computing.
General-purpose Premium NAS file systems are suitable for latency-sensitive file sharing workloads that require low latency, such as container data persistence, AI training data storage, manufacturing simulation, and genetic computing.
General-purpose Capacity NAS file systems are suitable for cost-sensitive file sharing workloads that require moderate latency, such as database backup, log storage, Windows user directory, and Linux home directory.
Extreme NAS file systems are suitable for latency-sensitive Linux applications for enterprises, development and test environments for continuous integration and continuous deployment (CI/CD), high-performance web services, online education services, and online gaming services.
The storage class of a file system cannot be changed. For more information about the limits on file systems, see Limits.
Select file systems based on workloads
Symbol descriptions:
The check sign (✓) indicates that the current storage class supports the feature.
The cross sign (×) indicates that the current storage class does not support the feature.
Item | General-purpose NAS file systems | Extreme NAS file systems | ||||||
Storage class | Capacity | Premium | Performance | Standard | Advanced | |||
Protocol | NFS v3/4.0 | SMB 2.1/3.0 | NFS v3/4.0 | SMB 2.1/3.0 | NFS v3/4.0 | SMB 2.1/3.0 | NFS v3 | NFS v3 |
Client | Linux (recommended) and Windows | Windows (recommended) and Linux | Linux (recommended) and Windows | Windows (recommended) and Linux | Linux (recommended) and Windows | Windows (recommended) and Linux | Linux | Linux |
Maximum number of files | 1 billion | 1 billion | 1 billion | 1 billion | 1 billion | 1 billion | 0.5 billion | 0.5 billion |
Performance | ||||||||
Average latency for reading 4 KiB files from a single-socket server | 10 ms | 10 ms | 2 ms | 2 ms | 2 ms | 2 ms | 1.2 ms | 0.3 ms |
Average latency for writing 4 KiB files to a single-socket server | 10 ms | 10 ms | 2 ms | 2 ms | 2 ms | 2 ms | 1.2 ms | 0.3 ms |
Maximum read throughput | 10 GB/s | 10 GB/s | 20 GB/s | 20 GB/s | 20 GB/s | 20 GB/s | Read and write: 1.2 GB/s | Read and write: 1.2 GB/s |
Maximum write throughput | 5 GB/s | 5 GB/s | 5 GB/s | 5 GB/s | 5 GB/s | 5 GB/s | ||
Maximum IOPS | 15,000 | 15,000 | 30,000 | 30,000 | 30,000 | 30,000 | 200,000 | 200,000 |
Note The actual read throughput and write throughput are affected by input and output operations depending on the size of I/O data blocks. | ||||||||
Elasticity | ||||||||
Elastic scale-in | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | × | × |
Elastic scale-out | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ (A step size of 1 GiB is supported.) | ✓ (A step size of 1 GiB is supported.) |
Data security | ||||||||
Encryption at rest | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Encryption in transit | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | × | × |
AD domain control | × | ✓ | × | ✓ | × | ✓ | × | × |
ACL-based access control | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | × | × |
Enterprise-grade features | ||||||||
Quotas | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | × | × |
Subdirectory-based mounting | × | × | × | × | × | × | × | × |
Recycle bin | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | × | × |
Lifecycle management | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | × | × |
Multi-zone high availability or active-active disaster recovery | × | × | × | × | × | × | × | × |
Backup | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Snapshots | × | × | × | × | × | × | ✓ | ✓ |