This topic describes the memory and disk requirements of OceanBase Migration Service (OMS).
Standard resource specifications for basic services and database management
| Resource type/Component | Basic services | Database management | Total |
|---|---|---|---|
| CPU | 1 core | 4 cores | 5 cores |
| Memory | 1 GB | 7 GB | 8 GB |
| Disk | 100 GB | 100 GB | 200 GB |
Data migration and synchronization between databases
The following table shows standard resource specifications of OMS components for the data migration from a MySQL database to a MySQL tenant of OceanBase Database.
| Resource type/Component | Store | Incr-Sync | Full-Import | Total |
|---|---|---|---|---|
| CPU | 4 cores | 2 cores | 2 cores | 8 cores |
| Memory | 8 GB | 8 GB | 4 GB | 20 GB |
| Disk | Depending on the generation speed of incremental logs at the database and the retention period of incremental data in OMS | 5 GB | 5 GB | >10 GB |
Data synchronization between a database and a big data source
Stores are reused within an OceanBase cluster in OMS earlier than V2.1.0 and within an OceanBase Database tenant in OMS V2.1.0 and later. You do not need to add additional stores for databases or tables that belong to one OceanBase cluster. You only need to add Incr-Sync resources for the synchronization links. In the case of large transactions, Incr-Sync components are extended as required.
The following table shows standard resource specifications of OMS components for the data migration from an OceanBase database to a Kafka instance.
| Resource type/Component | Store | Incr-Sync | Total |
|---|---|---|---|
| CPU | 4 cores | 2 cores | 6 cores |
| Memory | 8 GB | 4 GB | 12 GB |
| Disk | Depending on the generation speed of incremental logs at the database and the retention period of incremental data in OMS | 5 GB | >5 GB |
Resource specifications
Components for full operations
A data migration project involves the store component for pulling incremental data, Incr-Sync component for synchronizing incremental data, Full-Import component for importing full data, and Full-Verification component for verifying full data. However, the full migration and full verification processes do not run at the same time. Therefore, when link resource usage is estimated, only one of Full-Import and Full-Verification is considered.
Disk estimation
Most disk resources of OMS are used to cache incremental logs in OMS. Incremental data can be pulled and then migrated.
If 1 TB of logs are archived per day, OMS parses less than 1 TB of business data. Therefore, we recommend that you set the OMS log cache capacity to 1 TB.