This topic describes the instance specifications and performance benchmarks of the OceanBase data transmission service. It also provides instructions for upgrading the instance specification for a data migration or data synchronization task.
Usage notes
The specifications described in this topic are based on test data. They are provided for reference only and are not part of the service level agreement (SLA).
Each instance specification offers different performance levels for incremental synchronization, measured in RPS, and has a recommended maximum number of table objects. The data transmission service is designed to synchronize data to the target within seconds. However, actual latency may increase due to factors such as source instance workload, network bandwidth, network latency, and target instance write capacity. Therefore, sub-second latency cannot be guaranteed.
Key concepts
Instance specification: The data transmission service provides various performance tiers, known as instance specifications. The performance is primarily measured by the number of records synchronized.
RPS (Records Per Second): The number of data rows synchronized to the target table per second during incremental synchronization. For example, if 5,000 rows are synchronized from the source database to the target table per second, the RPS is 5,000.
Table object: The recommended maximum number of tables for a data migration or data synchronization task. This is calculated based on the assumption that each table object has a maximum of 50 columns.
Specifications
The data transmission service offers five instance specifications: MICRO, SMALL, MEDIUM, LARGE, and XLARGE, each offering a different level of performance for migration and synchronization. To reach the incremental synchronization performance ceilings listed in the table, the following conditions must be met:
The load on the source instance must be greater than or equal to the performance ceiling of the selected specification.
The write performance of the target instance must not create a bottleneck.
The network latency between the source or target instance and the data transmission service must be 2 ms or less.
The number of table objects for migration or synchronization must be less than or equal to the recommended maximum number listed in the table.
Instance specification
RPS limit
Throughput limit (MiB/s)
Maximum table objects
MICRO
300
0.3
100
SMALL
3,000
3
2,000
MEDIUM
5,000
5
40,000
LARGE
10,000
10
100,000
XLARGE
25,000
25
200,000
NoteActual performance depends on factors like the network environment, the performance of the source and target instances, and network latency. These performance values are for reference only and are not guaranteed by the SLA.
Upgrade instance specification
If the current instance specification no longer meets your needs, you can upgrade it for your data migration or data synchronization task.
Limitations
You cannot downgrade the instance specification for a data migration or data synchronization task.
You can upgrade a data migration task only when it is Running and in the incremental synchronization or reverse increment step.
You can upgrade a data synchronization task only when it is Running and in the incremental synchronization step.
While a data migration task is in the Configuration changing state, you cannot initiate a forward switchover or modify its migration objects.
While a data synchronization task is in the Configuration changing state, you cannot modify its synchronization objects.
For migrations from a PolarDB-X 1.0 database to an OceanBase Database MySQL tenant, if one instance is tied to multiple tasks, you can upgrade its specification only when all associated tasks are running normally in the incremental synchronization or reverse increment step.
Procedure
Log on to the ApsaraDB for OceanBase console .
In the left-side navigation pane, click Data Transmission > Data Migration.
This topic uses a data migration task as an example. For a data synchronization task, navigate to Data Transmission > Data Synchronization and follow the same steps on the Synchronization Tasks page.
On the Migration Tasks page, find the desired task, click ... in the Actions column, and select Upgrade.
Alternatively, click the task name to open its details page, and then click ... in the upper-right corner, and select Upgrade.
(Optional) In the dialog box that appears, click OK.
If you enable throttling for the Incremental Synchronization or Reverse Increment step of a data migration task, or the Incremental Synchronization step of a data synchronization task, you need to click OK in the pop-up dialog box. If throttling is not enabled, you are taken directly to the configuration change page.
On the Upgrade Specifications page, select a new instance specification and select the I have read and agree Data Transmission - Pay-as-you-go Terms of Service checkbox.
Click Buy Now.
After the purchase is complete, return to the Migration Tasks or Synchronization Tasks page. The task's new instance specification will be displayed.