This topic describes the specifications of each data migration channel and provides performance testing results.

Precautions

The performance indicators provided in this document are only used for reference and are not used as a criterion for product SLA evaluation.

Terms

Term Description
specification DTS provides data migration channels that have different specifications. The performance of these channels depends on the performance of incremental data migration.
table quantity The total number of tables in the test model.
record size The size of each record that is migrated during incremental data migration.
RPS The number of records per second (RPS) that are changed by INSERT, UPDATE, and DELETE operations in the source database.
Note
  • If an SQL statement contains operations on multiple rows of data, DTS identifies the operations as multiple data changes. If you perform INSERT, UPDATE, and DELETE operations on a data record multiple times, DTS also identifies the operations as multiple data changes.
  • DTS identifies each COMMIT operation as a data change.

Test model

Test procedure: Create an incremental migration task between two ApsaraDB RDS for MySQL instances. Then, perform a stress test on the source ApsaraDB RDS for MySQL instance to view the performance of incremental data migration.

Table 1. Test environment
Instance RDS instance configuration Maximum performance
Source instance
  • Instance type: rds.mys2.8xlarge
  • Memory: 48,000 MB
  • Maximum connections: 2,000
  • Maximum QPS: 18,000
  • Maximum IOPS: 14,000
Destination instance
  • Instance type: rds.mys2.8xlarge
  • Memory: 48,000 MB
  • Maximum connections: 2,000
  • Maximum QPS: 18,000
  • Maximum IOPS: 14,000

Test model:

  • The number of test tables is 20.
  • Each test table has a primary key.
  • The record size is 1 KB.
  • Each transaction has an average of two DML operations and one COMMIT operation. The ratio of INSERT, UPDATE, and DELETE operations is 3:1:2.

Test results

Source instance region Destination instance region Network latency between instances (milliseconds) Specification TPS QPS
China (Hangzhou) China (Hangzhou) 0.26 small 2,566 8,981
China (Hangzhou) China (Hangzhou) 0.26 medium 4,726 16,541
China (Hangzhou) China (Hangzhou) 0.26 large 6,378 23,204
China (Hangzhou) China (Qingdao) 26 small 2,469 8,641
China (Hangzhou) China (Qingdao) 26 medium 4,856 16,996
China (Hangzhou) China (Qingdao) 26 large 5,439 20,400
China (Hangzhou) China (Beijing) 26 small 2,533 8,866
China (Hangzhou) China (Beijing) 26 medium 5,038 17,633
China (Hangzhou) China (Beijing) 26 large 6,829 26,100
China (Hangzhou) US (Silicon Valley) 175 small 1,753 6,135
China (Hangzhou) US (Silicon Valley) 175 medium 2,837 9,929
China (Hangzhou) US (Silicon Valley) 175 large 3,884 15,500
Singapore US (Silicon Valley) 198 small 1,104 4,000
Singapore US (Silicon Valley) 198 medium 1,724 6,334
Singapore US (Silicon Valley) 198 large 2,256 8,300
Note The preceding test results show the maximum performance of data migration channels that are configured with different specifications. The performance of incremental data migration cannot be guaranteed in the following cases: The table to be migrated does not have a primary key, the network latency is high, an update hotspot exists, or the source and destination instances have performance bottlenecks.