CPFS AI-Computing Edition provides high-performance file access over RDMA through a Virtual Storage Channel (VSC), delivering single-node throughput of up to tens of GB/s. VSC is recommended for high I/O scenarios such as large model training and inference data loading. If a compute node and a file system are not in the same storage-compute affinity domain, use a VPC mount target instead.
What is VSC?
Virtual Storage Channel (VSC) is a high-performance storage access technology developed by Alibaba Cloud. It uses the RDMA protocol to provide compute nodes with low-latency, high-throughput access to file systems.
Key features
-
RDMA passthrough access: Unlike the traditional TCP/IP stack, VSC minimizes CPU overhead and significantly reduces end-to-end latency.
-
High throughput: Maximizes file system performance. Single-node throughput scales with instance specifications.
-
Flexible compute-storage relationship: Manage the attachment between an instance and a file system with
attachanddetachoperations, without configuring a network environment. A single VSC channel can attach to multiple file systems simultaneously.
For detailed performance metrics, including throughput, IOPS, and latency, see Product Specifications.
Typical use cases
-
Reading and writing checkpoints for large model training
-
Loading models for inference services
-
High-concurrency data preprocessing
-
Other I/O-sensitive AI computing tasks
VSC resource model
You manage the VSC high-speed access channel as a resource in the console and through OpenAPI.
-
One compute node corresponds to one VSC high-speed access channel.
-
One VSC high-speed access channel can attach to multiple CPFS AI-Computing Edition file systems.
VSC channel management follows the principle of "compute manages the channel, storage manages attachments":
|
Responsibility |
Actions |
Owner |
|
Channel lifecycle management |
Create, read, update, and delete |
Compute product OpenAPI |
|
Storage attachment management |
|
CPFS OpenAPI |
VSC and VPC access comparison
CPFS AI-Computing Edition supports both VSC and VPC access methods. VSC is the recommended method; use VPC for supplementary access across storage-compute affinity domains.
|
Feature |
VSC high-speed access |
VPC access |
Description |
|
Network protocol |
RDMA |
TCP |
RDMA provides lower end-to-end latency and less CPU overhead. |
|
Use cases |
The Lingjun cluster ID of the compute node is in the list of HPNZones associated with the file system. |
Access across storage-compute affinity domains or availability zones. |
Use the |
|
VPC mount target required? |
No |
Yes |
VPC access requires creating a VPC mount target. |
|
Performance |
High throughput, low latency |
Best-effort basis, with no Service Level Agreement (SLA). |
For specific metrics, see Product Specifications. |
Conceptual differences:
-
VSC: Establishes a direct attach relationship between an instance and a storage resource without a network layer abstraction, resulting in lower performance overhead.
-
VPC: First establishes a virtual private cloud, then connects compute and storage resources to the network. Access control relies on Access Control Lists (ACLs) and security groups.
Recommendation: When your compute nodes and CPFS AI-Computing Edition file system are in the same storage-compute affinity domain, use VSC high-speed access for optimal performance.
Determining VSC compatibility
A compute node can use VSC to access a CPFS AI-Computing Edition file system only if both are in the same storage-compute affinity domain. To verify compatibility:
-
Query the list of HPNZones associated with the file system: Call the CPFS API operation
DescribeFileSystemAssociatedHpnZones. Pass the file system ID to retrieve a list of Lingjun cluster IDs (HPNZones) that support VSC access for that file system. -
Identify the HPNZone of the compute node: Check the Lingjun cluster ID of your compute node in the Lingjun or PAI console.
-
Compare the results:
-
If the HPNZone of the compute node is in the list, you can use VSC high-speed access.
-
If the HPNZone of the compute node is not in the list, this indicates access across storage-compute affinity domains. You must use VPC access, which requires you to create a VPC mount target.
-
Note: A single file system can be associated with multiple HPNZones. VSC support does not require an exact HPNZone match. Always refer to the list returned by the DescribeFileSystemAssociatedHpnZones API operation.
APIs
The following CPFS OpenAPI operations manage VSC high-speed access channel and file system associations:
|
API |
Description |
|
AttachVscToFilesystems |
See the API reference: Attach VSC to File Systems. |
|
DetachVscFromFilesystems |
See the API reference: Detach VSC from File Systems. |
|
DescribeFilesystemsVscAttachInfo |
See the API reference: Query VSC Attachment Information. |
Note: The creation and deletion of a VSC high-speed access channel are managed through the OpenAPI of the respective compute product. For more information, see the documentation for that compute product.