Introduction

This document describes how to perform tuning for OceanBase on a Kunpeng server running openEuler.

OceanBase Database is a native, enterprise-class distributed database developed independently by the OceanBase team. It provides financial-grade high availability on commodity hardware and introduces a new city-level disaster recovery standard known as "Five IDCs across Three Regions". As the world's first distributed database to pass the TPC-C benchmark test, it can support over 1,500 nodes in a single cluster. It features cloud native and strong consistency with its enterprise edition compatible with Oracle and MySQL and community edition compatible with MySQL.

OceanBase Database includes the following common components:

• OceanBase Deployer (OBD): an installation and deployment tool for OceanBase open source software. OBD is also a package manager that can be used to manage all open source software of OceanBase. For details about the official documents, see https://en.oceanbase.com/docs/community-obd-en-10000000000842674.
• OBServer: the process name of OceanBase Database.
• OBClient: a client connection tool provided by OceanBase. As OceanBase (community edition) is compatible with MySQL, the MySQL client tool can be used to connect to OceanBase.
• OceanBase Database Proxy (ODP): a dedicated proxy server for OceanBase Database. It is also called OBProxy. For details about the official documents, see https://en.oceanbase.com/docs/community-odp-en-10000000000864196.

  OBProxy records the data distribution information of OBServer. The user's SQL request is sent to ODP first. ODP forwards the SQL request to the optimal OBServer, and then returns the execution result to the user, as shown in Figure 1. This method is more efficient than directly forwarding the SQL requests to nodes that do not contain the to-be-queried data.

  Figure 1 OceanBase data forwarding mode