After data migration is completed, but before the database is switched to OceanBase Database, you can perform a performance assessment. This topic describes how to create a full performance assessment task.
Background information
A performance evaluation task can be of the following types: Full Assessment, SQL File Parsing, and SQL File Replay. A full performance evaluation task can automatically schedule parsing and replay tasks. After the parsing task is completed, the system automatically initiates a replay task. You can choose to run the entire process or independently parse the files and replay the load. To independently create an SQL file replay task, you must first complete the full file parsing.
Currently, performance evaluation supports replay from an AWS Aurora MySQL database and an AWS MySQL database, a Huawei Cloud RDS MySQL database and a DWS database, an Alibaba Cloud RDS MySQL database and a PolarDB MySQL database, and a GCP MySQL database to an OceanBase database.
Prerequisites
Before you create a full performance evaluation task, you need to obtain the audit logs of the source database.
If you set Source Database Type to Aurora MySQL, AWS_MYSQL, RDS_MYSQL, POLAR_MYSQL, or GCP_MYSQL, for more information, see Obtain the traffic file of a database instance.
If you set Source Database Type to HUAWEI_RDS_MySQL, for more information, see Enable SQL audit logs.
If you set Source Database Type to HUAWEI_DWS, for more information, see Obtain audit logs of a database instance.
Before you perform an SQL file replay task, you must enable the SQL audit feature on the target OceanBase Database. For more information, see Enable SQL audit.
Limitations
Performance evaluation is supported only for cluster instances. Shared instances are not supported.
Only users with the Project Admin or Data Services Admin role can create a full performance evaluation task.
Procedure
Create a full performance assessment task.
Log in to the OceanBase Cloud console.
In the left-side navigation pane, click Data Services > Migrations.
On the Migrations page, click the Assess Performance tab.
On the Assess Performance tab, click Create > Full Assessment.
On the Set Up Source Database page, configure the parameters.
Parameter Description Assessment Task Name The name of the assessment task, which must be 30 characters or fewer. Instance Source Currently, AWS, HUAWEI, ALIYUN, and Google Cloud are supported. Source Database Type - If you set Cloud Vendor to AWS, the source database type can be Aurora MySQL or AWS_MYSQL.
- If you set Cloud Vendor to HUAWEI, the source database type can be HUAWEI_RDS_MySQL or HUAWEI_DWS.
- If you set Cloud Vendor to ALIYUN, the source database type can be RDS_MYSQL or POLAR_MYSQL.
- If you set Cloud Vendor to Google Cloud, the source database type can be GCP_MYSQL.
Region The region where the source database is located. Source Database Instance If you set Source Database Type to Aurora MySQL, AWS_MYSQL, HUAWEI_DWS, RDS_MYSQL, POLAR_MYSQL, or GCP_MySQL, you must enter the source database instance. For more information about how to obtain the name of a database instance, see Obtain a database instance.
Separate multiple database instances with commas (,).Source Database This parameter is displayed only when you set Cloud Vendor to Google Cloud. Click Next. On the Configure Data Collection page, configure the parameters.
If the Cloud Vendor is Google Cloud, Data Collected From supports only Import Object Storage (Google Cloud Object Storage).
If the Cloud Vendor is AWS, Data Collected From supports S3 Import and Upload File.
If the Cloud Vendor is ALIYUN, Data Collected From supports Import Object Storage (OSS) and Upload File.
If you store the audit logs of the Aurora MySQL instance or AWS MySQL instance in S3, or store the audit logs of the Alibaba Cloud RDS_MySQL instance or Polar_MySQL instance in OSS, select S3 Import or Import Object Storage (OSS) to import the audit logs for assessment. For more information about how to obtain the audit logs of the GCP MySQL instance, Aurora MySQL instance, AWS_MySQL instance, RDS_MySQL instance, and Polar_MySQL instance, see Obtain the traffic file of a database instance.
Note
We recommend that you create a dedicated user for the migration assessment service and grant only the required permissions to the bucket. For more information about Alibaba Cloud's account system, see Access Control.
Parameter Description AccessKey ID The AccessKey ID of the S3, Google Cloud Storage (GCS), or Alibaba Cloud account. For more information about the AccessKey ID of S3 or GCS, see Create an AccessKey. For more information about the AccessKey ID of Alibaba Cloud, see Create an AccessKey. AccessKey Secret The AccessKey Secret of the S3, GCS, or Alibaba Cloud account. S3/OSS Bucket Enter the name of the S3 or OSS bucket for log import. Bucket for File Import Enter the name of the GCP bucket for file import.
This parameter is displayed only when the Cloud Vendor is Google Cloud.File Directory Enter the directory for delivering the audit logs. Traffic Collection Time Range Select the time range to be assessed, which can be up to 24 hours.
If the data obtained is empty, no log file is generated in the selected time range.After you configure the preceding parameters, click Verify. After the verification is passed, the Valid File List displays the files that can be parsed.
If you store the audit logs of the Aurora MySQL instance or AWS MySQL instance or the traffic files of the Log Service SLS instance on your local server, or the Cloud Vendor is HUAWEI, select Upload File to manually import the audit logs in the ZIP or GZ format. Note that the maximum file size is 5 GB and only one file can be uploaded.
Click Next. On the Set Up Target Database page, configure the parameters.
Parameter Description Region The region of the target instance is the same as that of the source instance. Target Database Instance Confirm that the schema, data, and original instance of the target instance are consistent to ensure that the stress test traffic is executed normally. Tenant (Optional) Select the tenant ID of the target instance from the drop-down list. Target Account The username of the target database. For more information about the user privileges, see User privileges for replay. Password The password of the target database. After you configure the preceding parameters, click Verify. After the verification is passed, the Database List of Target End displays the databases that can be replayed. Select the name of the database to be replayed and click > to add it to the right-side Target list.
Click Next. After you confirm that the database of the target instance is the same as that in the traffic file, click OK in the dialog box that appears.
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 (x) Select the target replay speed from the drop-down list. The maximum speed is 10x.
The replay speed indicates the compression of QPS or TPS of traffic into a time range. For example, a replay speed of 2 indicates that the traffic to be replayed for 4 hours is replayed in 2 hours.Sampling Rate Select the target sampling rate from the drop-down list. The maximum sampling rate is 100%. Simulate Concurrency Simulate concurrency is enabled by default. Click Next to perform a precheck.
After the precheck is passed, click Start Now to start the performance assessment task.
After the task is started, you can view the assessment report on the Task List page. For more information, see View an assessment report. The files that are parsed are displayed on the Assess Performance > Parse files page.
Notice
When you start the replay, OceanBase Database automatically adds a allowlist group with a name in the omaxxx format to the OceanBase instance that you specified, to ensure that the server running the performance assessment task can connect to the OceanBase instance.