Performance tuning

You can tune the performance of OBLOADER from three aspects: command-line options, virtual machine (VM) memory, and database kernel.

Command-line options-based performance tuning

• Decrease the value of the --batch option when you import wide tables or tables with columns that contain long values. Default value: 200.

• Increase the value of the --batch option when you import narrow tables or tables with columns that contain short values. Default value: 200.

• You can adjust the value of the --thread option when the server load and network workload are relatively low.

Note

During performance tuning, take into account the resource usage on the server of OBLOADER, 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 script to 60% of the available physical memory.

The following table describes the VM memory parameter.

Database kernel-based performance tuning

You can tune the performance of OBLOADER by adjusting the following database kernel parameters:

-- Required system variables and parameters
set global ob_sql_work_area_percentage=30; -- Default value: 5
alter system set freeze_trigger_percentage=30; -- Default value: 70
set global max_allowed_packet=1073741824; -- Set it to 1 G

-- Optional system variables and parameters
alter system set enable_syslog_recycle='True'; -- Default value: false
alter system set max_syslog_file_count=100; -- Default value: 0
alter system set minor_freeze_times=500; -- Default value: 5
alter system set minor_compact_trigger=5; -- Default value: 5
alter system set merge_thread_count=45; -- Default value: 0
alter system set minor_merge_concurrency=20; -- Default value: 0
alter system set writting_throttling_trigger_percentage=85; -- Default value: 10