This topic describes the specifications and performance of the data transmission service of ApsaraDB for OceanBase.
Considerations
The specifications provided in this topic are based on test data and for your reference only, but do not constitute criteria for evaluating the service level agreement (SLA) of the data transmission service.
The records per second (RPS) performance of incremental synchronization and the recommended maximum number of table objects to migrate or synchronize vary based on the instance specification. The data transmission service allows you to synchronize data to the destination with a seconds-level latency. However, a seconds-level latency cannot be absolutely ensured because the latency of a migration or synchronization project is affected by a series of factors, including the running load of the source instance, bandwidth of the transmission network, network latency, and write performance of the destination instance.
Terms
Specification: The data transmission service provides specifications with different performance measured by the number of synchronized records.
RPS: the number of incremental data rows synchronized to the destination table per second. For example, if 5,000 incremental data rows in the source database are synchronized to the destination table per second, the RPS value is 5,000.
Table object: the unit for data migration and synchronization. The recommended maximum number of table objects to migrate or synchronize is calculated by assuming that each table object contains a maximum of 50 fields.
Specifications
The data transmission service provides five specifications based on the migration/synchronization performance ceiling: Micro, Small, Medium, Large, and XLarge. The performance ceiling for incremental synchronization can be reached only when the following conditions are met:
The load of the source instance is greater than or equal to the performance ceiling of the corresponding specification.
The destination instance is not bottlenecked by the write performance and can handle the performance stress of different specifications.
The network latency between the source/destination instance and the data transmission service is less than or equal to 2 ms.
The number of table objects to migrate or synchronize is smaller than or equal to the recommended maximum value provided in the following table.
Specification
Maximum RPS (for reference only)
Recommended maximum number of table objects
Micro
300
100
Small
3,000
2,000
Medium
5,000
40,000
Large
10,000
100,000
XLarge
25,000
200,000
NoteThe online performance is subject to various factors such as the network environment, the performance of the source and destination instances, and the network latency. Therefore, the actual performance values can vary slightly. The performance ceilings provided in the preceding table are for reference only and do not constitute any commitment of the SLA.