When container images are automatically or manually replicated between the Chinese mainland and regions outside Chinese mainland, or between the Chinese mainland and the China (Hong Kong) region, the image replication speed may be slow. Container Registry provides the cross-border replication acceleration feature to accelerate image replication. This topic describes how to use the cross-border replication acceleration feature.
You cannot replicate images from a public cloud region to a non-public cloud region, such as a Alibaba Cloud Finance region or a Alibaba Gov Cloud region.
Enable cross-border replication acceleration
Log on to the Container Registry console.
In the top navigation bar, select a region.
In the left-side navigation pane, click Instances.
On the Instances page, click the Enterprise Edition instance that you want to manage.
On the management page of the Container Registry Enterprise Edition instance, choose .
In the upper-left corner of the Instance Replication page, turn on Cross-border Replication Acceleration.
In the Tips message, click OK.
After you enable the cross-border replication acceleration feature, you can create a replication rule to replicate images from an instance to another instance. For more information, see Replicate images between instances that belong to the same account and Replicate images between instances that belong to different accounts. When images are replicated, Container Registry automatically uses the cross-border replication acceleration feature.
Reference data for cross-border acceleration
The following table describes the latency of image replication in March 2022 after cross-border replication acceleration is enabled. The table collects the TP95 replication latency values of single-layer 1 GB images in different regions around the world. The latency values do not include the queue time of additional replication tasks beyond the maximum allowed concurrent replication tasks. In this example, the China (Hangzhou) region is used to represent the Chinese mainland.
TP95 refers to the maximum latency of the 95th percentile of image replication tasks. For example, assume that 100 tasks have been executed. The latencies of the tasks are sorted in ascending order, and then the 95th value is taken as the TP95 value.
The cells in the preceding table are color-coded based on the latency of replication tasks.
Green: The latency is not greater than 30 seconds.
Blue: The latency is greater than 30 seconds and not greater than 1 minute.
Yellow: The latency is greater than 1 minute and not greater than 2 minutes.
Orange: The latency is greater than 2 minutes and not greater than 3 minutes.
View link types
To view the type of the link used by a replication task, in the left-side navigation pane, choose . Link types include:
Default Link: the default link of Container Registry Enterprise Edition instances.
Cross-border Acceleration Link: On the link, the cross-border replication acceleration feature is enabled to accelerate image replication.
References
For information about how to create a replication task by calling an API operation, see CreateRepoSyncTaskByRule and CreateRepoSyncTask.