This topic describes the recommended configurations for several typical scenarios, including Express OLTP, Complex OLTP, HTAP, OLAP, and OBKV.
To ensure good performance of OceanBase Database in various business scenarios, OceanBase summarizes the recommended configurations for core parameters and variables based on its extensive experience in optimizing real-world scenarios. These recommended configurations are included in the installation package and can be viewed after deployment. Additionally, to make it easier for users to apply these configurations, parameter templates are supported in OceanBase Cloud Platform (OCP) and OceanBase Deployer (obd). When creating clusters and tenants using OCP or obd, users can directly select the corresponding parameter template to complete the settings.
Parameter configuration templates
After installing the OceanBase Database RPM package, you can view the parameter configuration templates for different business scenarios in the /home/admin/oceanbase/etc directory.
default_parameter.json: This file stores the recommended configurations for parameters.default_system_variable.json: This file stores the recommended configurations for system variables.
Scenario descriptions
Express OLTP
Express OLTP refers to real-time, interactive, high-frequency operations such as adding, deleting, modifying, and querying data in a database. It is commonly used in industries such as banking, retail, aviation, and hospitality to handle daily business operations such as bill payments, inventory management, and order processing. OLTP scenarios typically involve a large number of concurrent transactions and require the database to respond quickly and reliably to user requests.
For more information about the recommended configurations for this scenario, see Best practices for configuration.
Complex OLTP
Complex OLTP refers to scenarios that handle large volumes of data and complex transactions. It is commonly used in industries such as banking and insurance. These scenarios typically involve complex joins, complex correlated subqueries, batch processing jobs written in PL/SQL, and long or large transactions. Sometimes, parallel execution strategies are used to accelerate short-running queries.
For more information about the recommended configurations for this scenario, see Best practices for configuration.
HTAP
HTAP stands for Hybrid Transaction/Analytical Processing. It refers to a database management system or architecture that supports both Online Transaction Processing (OLTP) and Online Analytical Processing (OLAP). HTAP is used in business environments that require real-time data analysis and querying, such as financial transactions, retail, and logistics. These industries require efficient transaction processing and real-time data analysis and querying capabilities to support business decision-making and analysis. The advantage of HTAP architecture is that it reduces the costs of data replication and transformation and provides real-time data analysis capabilities, accelerating the business decision-making process.
For more information about the recommended configurations for this scenario, see Best practices for configuration.
OLAP
OLAP stands for Online Analytical Processing. It is a data processing technology used for multidimensional analysis of large datasets. It allows users to perform complex analyses from different perspectives, including dimensions, metrics, filters, and sorting. OLAP helps users identify and understand patterns, trends, and associations in data, supporting decision-making and business intelligence. OLAP technology is commonly used in data warehouses and business intelligence systems.
For more information about the recommended configurations for this scenario, see Best practices for configuration.
OBKV
OBKV is a multi-model key-value (KV) product of OceanBase Database. It is mainly used to provide low-cost storage for large-scale structured and semi-structured data and to achieve high access performance with simple operation interfaces. OBKV bypasses the SQL layer and directly uses the distributed storage of OceanBase Database to build various multi-model KV forms. Between the distributed storage and the multi-model forms, OBKV has a framework layer called TableAPI that provides encapsulated storage and transaction call capabilities to the model layer.
For more information about the recommended configurations for this scenario, see Best practices for configuration.
References
- For more information about parameters and system variables, see Overview of parameters and system variables.
- For more information about how to set parameters, see Set parameters.
- For more information about how to set variables, see Set variables.