Tuning Process

Locate the real problems, analyze performance bottlenecks, and select the most appropriate tuning method.

Identify problems, find performance bottlenecks, and determine a tuning method based on the bottleneck level.

Figure 1 shows the OceanBase database tuning flow.

Figure 1 Tuning process

The tuning analysis process is as follows:

In most cases, even before the entire pressure test traffic enters the server, the pressure test result may fail to meet the expectation due to network factors, such as the bandwidth, maximum number of connections, and limit on the number of new connections.
Check whether the key metrics meet the requirements. If not, locate the cause. Generally, you can locate the cause on servers (in most cases) or clients (in a few cases).
If the problem cause is on a server, check the hardware metrics such as the CPU, memory, drive I/O, and network I/O metrics. If any abnormal hardware metric is detected, further analysis is required.
If the hardware metrics are normal, check the database metrics, such as the wait events and memory hit rate.
If hardware and database metrics are normal, check the algorithms, buffer, cache, synchronization, and asynchronization. If any abnormal metric is detected, further analysis is required.
For the OceanBase database, allocate sufficient resources (such as CPU and memory) to the corresponding tenant. Otherwise, the expected performance may not be achieved.

Table 1 lists the possible bottlenecks.

**Table 1** Possible bottlenecks
Bottleneck	Description
Hardware/Specifications	Check the CPU, memory, and drive I/O metrics for hardware bottlenecks and network bottlenecks (network bottlenecks can be ignored in a LAN).
OS	Check for problems related to the operating system, such as Windows, UNIX, or Linux. For example, if the physical memory capacity is insufficient and the virtual memory capacity setting is improper during a performance test, the virtual memory swap efficiency may be greatly reduced. As a result, the response time is significantly increased, causing a bottleneck that is considered an OS bottleneck.
Database	Check the database configurations. For example, improper parameter settings may cause insufficient resource allocation during tenant creation.

Parent topic: Tuning Introduction