You can tune the performance of OBDUMPER from three aspects: command-line options, virtual machine (VM) memory, and database kernel.
Command-line options-based performance tuning
You can tune the performance of OBDUMPER by adjusting settings of the following options:
Option |
Default value |
Description |
|---|---|---|
| --thread | CPU * 2 | The number of concurrent threads for data export. You can adjust the value of this option based on the actual situation. |
| --page-size | 10000 | The number of rows to return in a query. You can adjust the value of this option based on the actual situation. Example: --page-size 20000. |
Note
During performance tuning, take into account the resource usage on the server of OBDUMPER, the OBProxy server, and OBServers in the OceanBase cluster. You only need to consider the network condition of the OBProxy server.
VM memory-based performance tuning
We recommend that you set the VM memory parameter in the bat/shell script to 60%.
The following table describes the VM memory parameter:
Parameter |
Default value |
|---|---|
| -Xms4G -Xmx4G | 4 G |
Database kernel-based performance tuning
We recommend that you manually trigger a major compaction operation before you export data and export data after the major compaction is completed. For more information about major compaction, see the Major compaction management chapter of the OceanBase Database Administrator Guide.