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 status. |
| --page-size | 2000 | The page size for a single query. You can adjust the value of this option based on the actual status, for example, --page-size 10000. |
Note
During performance tuning, take into account the resource utilization on the server where OBDUMPER run and on the nodes in the OBServer cluster, and the network condition on the node where OBProxy runs.
VM memory-based performance tuning
Modify the VM memory parameter in the script. We recommend that you set the value of this parameter to 60% the size of the available physical memory when you export a large amount of data.
The following table describes the VM memory parameter:
| Parameter | Default value |
|---|---|
| -Xms4G -Xmx4G | 4G |
Database kernel-based performance tuning
We recommend that you manually trigger a major compaction operation before you export data, and export data after the minor compaction is completed. For more information about minor compaction, see Major compaction management in the Administrator Guide of OceanBase Database.