You can tune the performance of OBDUMPER from three aspects: command-line options, VM memory, and database kernel.
Command-line options-based performance tuning
You can tune the performance of OBDUMPER by adjusting the settings of options in the following table.
| Option | Default value | Description |
|---|---|---|
| --thread | Number of CPU cores × 2 | The number of concurrent threads for data export. You can adjust the value of this option based on the system resource utilization. |
| --page-size | 1000000 | The number of rows to return on a page. You can adjust the value of this option based on the system resource utilization. |
Note
During performance tuning, take into account the resource utilization on the server where OBDUMPER runs, on the ODP service nodes, and on the nodes in the OceanBase cluster, especially the network of the ODP nodes.
VM parameter-based performance tuning
Set the VM parameter in the export script to 60% of the available physical memory. Default value:-Xms4G -Xmx4G.
vim bin/obdumper
JAVA_OPTS="$JAVA_OPTS -server -Xms4G -Xmx4G -XX:MetaspaceSize=512M -XX:MaxMetaspaceSize=512M -Xss352K"
Database kernel-based performance tuning
We recommend that you manually trigger a major compaction before you export data and then export data after the major compaction is completed.
For more information about how to implement a major compaction, see the "Major compaction management" topic in Administrator Guide on the official website of OceanBase Database.
