CPFS General-purpose Edition offers two storage classes: 100 MB/s/TiB Baseline and 200 MB/s/TiB Baseline. This topic compares their performance metrics, supported advanced features, and dataflow performance for the same capacity to help you choose the class that best fits your business needs.
File system instance performance
CPFS General-purpose Edition supports access through CPFS-POSIX and CPFS-NFS clients. The following sections compare the throughput, IOPS, and I/O latency for each storage class at the same capacity across both client types.
Choose between CPFS-POSIX and CPFS-NFS
If you do not have extreme performance requirements, we recommend using a CPFS-NFS client for a better user experience. To do so, enable the General-purpose protocol service in the console.
CPFS-NFS supports the following operating systems:
Operating system | Operating system version |
Alibaba Cloud Linux |
|
CentOS |
|
Ubuntu |
|
Debian |
|
SUSE |
|
For workloads that require extreme performance, use a CPFS-POSIX client if your environment meets the following conditions:
You do not rely on the Container Storage Interface (CSI) to access CPFS.
You do not use mmap.
-
Your operating system is one of the following versions:
Operating system
Distribution
Kernel version
Alibaba Cloud Linux
Alibaba Cloud Linux 2.1903 64-bit
4.19.91-27.4.al7.x86_64 and earlier
RHEL or CentOS
8.4
4.18.0-305.19.1.el8_4
8.3
4.18.0-240.22.1.el8_3
8.2
4.18.0-193.28.1.el8_2
8.1
4.18.0-147.8.1.el8_1
8.0
4.18.0-80.11.2.el8_0
7.9
3.10.0-1160.42.2.el7
7.8
3.10.0-1127.19.1.el7
7.7
3.10.0-1062.18.1.el7
7.6
3.10.0-957.54.1.el7
7.5
3.10.0-862.14.4.el7
7.4
3.10.0-693.2.2.el7
7.3
3.10.0-514.26.2.el7
7.2
3.10.0-514.26.2.el7
Ubuntu
20.04.3 LTS
5.4.0-86-generic
CPFS-POSIX
CPFS file systems that use zone-redundant storage (ZRS) do not support the POSIX protocol.
After you create a CPFS-POSIX mount target, you can access the file system with a CPFS-POSIX client.
Check the performance of your file system based on its creation time, version number, and region.
For more information about how to view the version number of a file system, see View the version number of a file system.
After January 22, 2024
As of January 22, 2024, the performance of 100 MB/s/TiB Baseline and 200 MB/s/TiB Baseline file systems has been upgraded in select regions. Performance in other regions remains unchanged.
File systems created before this date are not automatically upgraded. To use the upgraded performance, create a new CPFS General-purpose Edition file system and migrate your data to it.
|
Metric |
100 MB/s/TiB Baseline |
200 MB/s/TiB Baseline |
||
|
File system version number |
v2.3.4 and later |
v2.3.4 and later |
||
|
Supported regions and zones |
|
|
|
|
|
Throughput |
min{0.1 × storage capacity (GiB), 30,000} MB/s |
min{0.1 × storage capacity (GiB), 20,000} MB/s |
min{0.2 × storage capacity (GiB), 45,000} MB/s Throughput can be increased up to 100,000 MB/s. To request a higher throughput, submit a ticket. |
min{0.2 × storage capacity (GiB), 20,000} MB/s Throughput can be increased up to 100,000 MB/s. To request a higher throughput, submit a ticket. |
|
IOPS |
min{15 × storage capacity (GiB), 3,600,000} |
min{15 × storage capacity (GiB), 2,800,000} |
min{30 × storage capacity (GiB), 7,200,000} IOPS can be increased up to 10,000,000. To request a higher IOPS, submit a ticket. |
min{30 × storage capacity (GiB), 2,800,000} IOPS can be increased up to 10,000,000. To request a higher IOPS, submit a ticket. |
|
Average single-stream 4k read latency |
0.6 ms |
0.4 ms |
||
|
Average single-stream 4k write latency |
0.8 ms |
0.6 ms |
||
Before January 22, 2024
If your file system was created before January 22, 2024, refer to the following performance metrics. To use the upgraded performance, create a new CPFS General-purpose Edition file system and migrate your data to it.
|
Metric |
100 MB/s/TiB Baseline |
200 MB/s/TiB Baseline |
|
File system region |
All supported regions |
All supported regions |
|
Throughput |
min{0.1 × storage capacity (GiB), 20,000} MB/s |
min{0.2 × storage capacity (GiB), 20,000} MB/s Throughput can be increased up to 100,000 MB/s. To request a higher throughput, submit a ticket. |
|
IOPS |
min{15 × storage capacity (GiB), 2,800,000} |
min{30 × storage capacity (GiB), 2,800,000} IOPS can be increased up to 10,000,000. To request a higher IOPS, submit a ticket. |
|
Average single-stream 4k read latency |
0.6 ms |
0.4 ms |
|
Average single-stream 4k write latency |
0.8 ms |
0.6 ms |
|
Metric |
100 MB/s/TiB Baseline |
200 MB/s/TiB Baseline |
||
|
File system version number |
v2.3.4 and later |
v2.3.4 and later |
||
|
Supported regions |
|
|
||
|
Throughput |
min{0.1 × storage capacity (GiB), 30,000} MB/s |
min{0.2 × storage capacity (GiB), 45,000} MB/s Throughput can be increased up to 100,000 MB/s. To request a higher throughput, submit a ticket. |
||
|
IOPS |
min{15 × storage capacity (GiB), 3,600,000} |
min{30 × storage capacity (GiB), 7,200,000} IOPS can be increased up to 10,000,000. To request a higher IOPS, submit a ticket. |
||
|
Average single-stream 4k read latency |
0.6 ms |
0.4 ms |
||
|
Average single-stream 4k write latency |
0.8 ms |
0.6 ms |
||
CPFS-NFS
After enabling the file storage CPFS protocol service, you can use a CPFS-NFS client to access a CPFS General-purpose Edition file system. This service provides NFSv3 mount targets that are independent of POSIX mount targets and is available in two types: General-purpose and Cache. The following table compares their performance metrics.
|
Protocol service type |
Metric |
100 MB/s/TiB Baseline (LRS) |
200 MB/s/TiB Baseline (LRS) |
100 MB/s/TiB Baseline (ZRS) This feature is available only to users on the whitelist. |
|
General-purpose |
Throughput |
Read/Write: min[100 × storage capacity (TiB), 20,000] MB/s |
Read/Write: min[200 × storage capacity (TiB), 20,000] MB/s |
|
|
IOPS |
Read/Write: min[4,000 × storage capacity (TiB), 960,000] |
Read/Write: min[8,000 × storage capacity (TiB), 960,000] |
|
|
|
Single-stream latency |
|
|
|
|
|
Maximum throughput per client |
600 MB/s |
600 MB/s |
300 MB/s |
|
|
Maximum IOPS per client |
|
|
|
|
|
Cache |
Throughput |
The maximum read bandwidth specified when creating the protocol service, up to 100 GB/s. |
The maximum read bandwidth specified when creating the protocol service, up to 100 GB/s. |
Not supported |
|
IOPS |
|
|
Not supported |
|
|
Single-stream latency |
|
|
Not supported |
|
|
Maximum throughput per client |
1.1 GB/s |
1.1 GB/s |
Not supported |
|
|
Maximum IOPS per client |
|
|
Not supported |
Dataflow performance
Dataflow is not supported on CPFS file systems that use zone-redundant storage.
CPFS General-purpose Edition supports dataflow between the file system and Object Storage Service (OSS). After creating a dataflow task, the file system automatically synchronizes object metadata from an OSS bucket. Once synchronized, you can use the high-performance, POSIX-compatible file interface to process the data in OSS. Data can also be exported from the file system to the OSS bucket through the console or OpenAPI.
|
Operation type |
Metric |
Description |
|
Data import |
Throughput for files larger than 1 GB |
|
|
OPS for megabyte-scale files |
Single-directory and multi-directory import: 1,000. |
|
|
Data export |
Throughput for files larger than 1 GB |
|
|
OPS for megabyte-scale files |
Single-directory and multi-directory export: 600. |
|
|
Data deletion |
OPS |
Single-directory and multi-directory deletion: 2,000. |
|
On-demand loading (lazy load) |
Throughput for files larger than 1 GB |
|
|
OPS for megabyte-scale files |
Single-directory and multi-directory import: 1,000. |
|
|
Automatic metadata update |
OPS |
|
Capacity specifications
Locally redundant storage (LRS)
Initial capacity: 3,600 GiB
Scaling step size: 1,200 GiB
Maximum capacity: 1 PiB
Zone-redundant storage (ZRS)
Initial capacity: 500 GiB
Scaling step size: 100 GiB
Maximum capacity: 89,600 GiB (approximately 88 TiB)