All Products
Search

This Product

    ApsaraDB for OceanBase:Create a full performance assessment task

    Document Center

    ApsaraDB for OceanBase:Create a full performance assessment task

    Last Updated:Dec 29, 2025

    After data migration, you can perform performance assessment before you switch your business applications to ApsaraDB for OceanBase. This topic describes how to create a full performance assessment task.

    Background

    Three types of performance assessment tasks are supported: Full Assessment, SQL File Parsing, and SQL File Replay. A full performance assessment task can automatically schedule a parsing task and a replay task. Traffic is automatically replayed after the parsing task is completed. You can choose to execute the entire process, or perform file parsing and workload replay separately. To create an SQL file replay task, you must specify a complete parsed file.

    The migration assessment service supports replay from a third-party data source, such as RDS_MySQL, PolarDB-X 1.0, PolarDB-X 2.0, TiDB, and POLARMYSQL, to an OB_MySQL data source. It also supports replay for upgrades within the same ApsaraDB for OceanBase compatible mode, which means replay from one OB_MySQL data source to another, or from one OB_Oracle data source to another.

    Limitations

    Only users with the AliyunOceanBaseFullAccess permission can create full performance assessment tasks. For more information about the permission policy, see AliyunOceanBaseFullAccess.

    Non-OceanBase database as the source

    1. Create a full performance assessment task.

      1. Log on to the

        ApsaraDB for OceanBase console.

      2. In the left-side navigation pane, choose Migration Assessment > Performance Assessment.

      3. On the Performance Assessment page, choose Create > Full Assessment in the upper-right corner.

    2. On the Set Up Source Database page, configure the parameters.

      Parameter

      Description

      Assessment Task Name

      The name of the assessment task. You can specify a custom task name.

      Cloud Vendor

      Select Alibaba Cloud Database from the drop-down list.

      Source Database Type

      Select the required database type from the drop-down list. You can select RDS_MySQL, PolarDB-X 1.0, PolarDB-X 2.0, TIDB, or POLARMYSQL.

    3. Click Next. Configure the parameters on the Configure Data Collection page.

      Data Collected From can be set to OSS Import or Upload File. Before performance assessment, you must obtain the traffic files of the RDS_MySQL, PolarDB-X, or POLARMYSQL instance and export the files to an Object Storage Service (OSS) bucket or save the files to your local storage. For more information, see Obtain the traffic files of an instance.

      Note

      • We recommend that you create a dedicated user for the migration assessment service and grant the user only privileges on relevant buckets. For more information about the Alibaba Cloud account system, see the documentation of Resource Access Management.

      • If you select TIDB for Source Database Type, only the Upload File option is supported for Data Collected From.

      • If you store SLS traffic files in an OSS bucket, select OSS Import to import traffic files for performance assessment.

        Parameter

        Description

        AccessKey Account

        The AccessKey ID of your Alibaba Cloud account.

        AccessKey Password

        The AccessKey secret of your Alibaba Cloud account.

        OSS Bucket for Log Import

        The name of the OSS bucket from which the logs are imported.

        File Directory

        The directory to which the traffic files are delivered.

        Traffic Collection Time Range

        The time period for assessment. Objects generated during the specified time period are assessed. The maximum time period is 24 hours.

        If no data is obtained, no log files were generated within the specified time range.

        Click Verify. After the verification succeeds, parsable files are displayed in Valid Files.

      • If you store SLS traffic files in the local storage, select Upload File and manually import a file in the corresponding format for assessment. You can upload only one file with a maximum size of 5 GB.

        • When the source database type is RDS_MySQL or PolarDB-X 2.0, valid values of File Type are SLS File and SQL Insight File.

          You can upload an SLS file in the JSON, CSV, or ZIP format, or an SQL insight file in the CSV or ZIP format.

        • When the source database type is PolarDB-X 1.0, you can upload a file in the CSV or ZIP format.

        • When the source database type is TIDB, you can upload a file in the JSON, CSV, LOG, or ZIP format.

        • When the source database type is POLARMYSQL, you can upload a file in the JSON, CSV, or ZIP format.

    4. Select the created instance from the Source Database Instance drop-down list and then click Next.

    5. On the Set Up Target Database page, configure the parameters.

      Parameter

      Description

      Target Database Instance

      Select the target database instance from the drop-down list. Make sure that the table schemas and data of the target instance are consistent with those of the source instance to ensure normal stress testing.

      Tenant

      Select the ID of the tenant where the target database instance resides from the drop-down list.

      Target Account

      The username of a user in the target database.

      Password

      The password of the database user.

      Click Verify. After the verification succeeds, you can view the list of databases to which the files can be replayed on the Target Database List page. Select the name of a target database and click > to add it to the right-side Target list.

    6. Click Next. On the Configure Workload Replay page, configure the parameters.

      Parameter

      Description

      Replay Type

      The replay type. Valid values: Read Traffic (DQL) and Write Traffic (DML).

      Replay Speed

      Select the replay speed from the drop-down list. Maximum replay speed: 10x.

      Replay at a higher speed increases the queries per second (QPS) and transactions per second (TPS) of traffic so that the replay can be completed within a shorter time frame. For example, if the replay speed is set to 2x, the time required to replay the same traffic can be reduced by half, such as from four hours to two hours.

      Sampling Rate

      Select the sampling rate from the drop-down list. Maximum sampling rate: 100%.

      Simulate Concurrency

      Specify whether to enable concurrency simulation. If you set the parameter to No, the replay speed will be slow.

    7. Click Next. The system automatically performs a precheck.

    8. After the precheck succeeds, click Start to execute the performance assessment task.

      After the task starts, you can view the assessment report on the Assessment Tasks tab. For more information, see View a performance assessment report. Parsed files are displayed on the Parsed Files tab of the Performance Assessment page.

      Important

      When you start replay, the migration assessment service automatically adds a whitelist named in the omaxxx format to the replay target instance that you selected. This ensures that the replay server can normally connect to your database.

    OceanBase database as the source

    1. On the Performance Assessment page, choose Create > Full Assessment in the upper-right corner.

    2. On the Set Up Source Database page, configure the parameters.

      Parameter

      Description

      Assessment Task Name

      The name of the assessment task. You can specify a custom task name.

      Cloud Vendor

      Select Alibaba Cloud Database from the drop-down list.

      Source Database Type

      The database type. Select OB_MySQL or OB_Oracle from the drop-down list.

      Source Database Instance

      Select a created database instance from the drop-down list.

      Tenant

      Select the ID of the tenant where the target database instance resides from the drop-down list.

    3. Click Next. Configure the parameters on the Configure Data Collection page.

      Important

      If SQL audit is disabled for the source tenant, data collection is not supported. Click Go open. On the SQL Audit page that appears, click Start SQL Audit.

      Parameter

      Description

      Data Collected From

      If the source database type is OB_MySQL or OB_Oracle, you can select Collect from Audit Views.

      Note

      This collection method is available for limited-time free trial.

      Traffic Collection Time Range

      You can select a start time and end time for data collection. A maximum span of 30 days is supported, and data in at most 24 hours can be parsed at a time.

      The time range is accurate to hours. You can select only a time range after SQL audit is enabled.

    4. Click Next. On the Set Up Target Database page, configure the parameters.

      Parameter

      Description

      Database Type

      ApsaraDB for OceanBase supports replay of upgrades in the same compatible mode.

      Target Database Instance

      Select the target database instance from the drop-down list. Make sure that the table schemas and data of the target instance are consistent with those of the source instance to ensure normal stress testing.

      Use Backup Data for Initialization

      If you select this option, a new instance is created for backup and restore. For more information, see the following table.

      Tenant

      If you do not select Use Backup Data for Initialization, select the ID of the tenant where the target database instance is located from the drop-down list.

      If you select Use Backup Data for Initialization, you need to configure the following parameters.

      Important

      The migration assessment service supports only restore from an earlier version to a later version. ApsaraDB for OceanBase V4.x does not support restore from a version earlier than V4.x.

      Parameter

      Description

      Restore Object

      The default value is Tenant.

      Source Cluster

      Select the source cluster for data restore from the drop-down list.

      Source Tenant

      Select the source tenant for data restore from the drop-down list.

      Restore Point in Time

      The point in time to which data is to be restored. The latest point in time to which data can be restored is displayed. You can select a point in time as needed.

      Target Instance

      Select from the drop-down list the instance to which the data is to be restored.

      Target Tenant Name

      Select from the drop-down list the tenant to which the data is to be restored.

      Resource Distribution Nodes

      The number of nodes for resource distribution. More nodes means higher reliability and availability. However, more nodes also require more overall distribution overheads. Select the number of nodes as needed.

      Single-node Resources

      The number of CPU cores and memory size allocated to a single node. You can click View Resource Distribution to view the resource distribution among the nodes.

      Note

      • The total CPU and memory capacities of all tenants cannot exceed the specifications of the cluster to which they belong.

      • Total resources available to a tenant = Single-node resources x Number of resource distribution nodes × Number of replicas

      VPC

      The ID of the virtual private cloud (VPC) to which the Elastic Compute Service (ECS) instance belongs.

      If no suitable VPC is available, create a VPC as prompted. For more information, see Create a VPC.

      Primary Zone

      The primary zone of the target tenant.

      vSwitch

      The ID of the vSwitch on the network to which the ECS instance belongs.

      If no suitable vSwitch is available, create a vSwitch as prompted. For more information, see Create a vSwitch.

      Remarks (optional)

      The remarks information about data backup and restore.

    5. Click Next. On the Configure Workload Replay page, configure the parameters.

      Parameter

      Description

      Replay Account/Password

      After you enter the replay account and password, click Verify.

      Replay Library

      Select a file from the Parsable Files list and click > to add it to the Target list on the right.

      Replay Type

      The replay type. Valid values: Read Traffic (DQL) and Write Traffic (DML).

      Replay Speed

      Select the replay speed from the drop-down list. Maximum replay speed: 10x.

      Sampling Rate

      Select the sampling rate from the drop-down list. Maximum sampling rate: 100%.

      Simulate Concurrency

      Specify whether to enable concurrency simulation. If you set the parameter to No, the replay speed will be slow.

      Read/Write Splitting

      Specify whether to enable read/write splitting.

    6. Click Next. The system automatically performs a precheck.

    7. After the precheck succeeds, click Start to execute the performance assessment task.

      After the task starts, you can view the assessment report on the Assessment Tasks tab. For more information, see View a performance assessment report. Parsed files are displayed on the Parsed Files tab of the Performance Assessment page.

      Important

      When you start replay, the migration assessment service automatically adds a whitelist named in the omaxxx format to the replay target instance that you selected. This ensures that the replay server can normally connect to your database.