This topic provides parameter configuration recommendations for several typical scenarios, including Online Transaction Processing (OLTP), Complex OLTP, Hybrid Transactional and Analytical Processing (HTAP), Online Analytical Processing (OLAP), and OBKV applications.
To ensure that OceanBase Database delivers optimal performance across various business scenarios, OceanBase has summarized recommended configurations for key parameters and variables based on extensive tuning experience from real-world use cases. These recommended configurations are included in the installation packages and can be viewed after deployment. Additionally, parameter templates are supported in both the OceanBase Cloud Platform (OCP) and OceanBase Deployer (obd). When creating a cluster or tenant using OCP or obd, you can directly select the corresponding parameter template for your scenario to complete the configuration.
Parameter configuration templates
After installing the OceanBase Database RPM package, you can find parameter configuration templates with recommended settings for different business scenarios in the /home/admin/oceanbase/etc directory.
default_parameter.json: Contains recommended configurations for parameters.default_system_variable.json: Contains recommended configurations for system variables.
Scenario introduction
Online Transaction Processing (OLTP)
Online Transaction Processing (OLTP) refers to real-time, interactive, high-frequency operations for 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 handling 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 Recommended configurations.
Complex OLTP
Complex OLTP is a scenario that involves processing large amounts of data and handling complex transactions. This scenario is commonly used in workloads for banking and insurance systems. These workloads typically involve complex joins, complex correlated subqueries, batch processing jobs written in PL/SQL, and long or large transactions. To accelerate short-running queries, parallel execution strategies are sometimes employed.
For more information about the recommended configurations for this scenario, see Recommended configurations.
HTAP scenario
HTAP refers to database management systems or architectures that support both online transactional processing (OLTP) and online analytical processing (OLAP). HTAP scenarios are common in business environments that require real-time data analysis and queries, such as finance, retail, and logistics. These industries need efficient transaction processing alongside real-time analytics to support business decision-making. The main advantage of the HTAP architecture is its ability to reduce the costs associated with data replication and transformation, deliver real-time analytics, and accelerate the decision-making process.
For more information about the recommended configurations for this scenario, see Recommended configurations.
OLAP scenario
OLAP is a data processing technology used for multidimensional analysis of large datasets. It allows users to perform complex analyses on data from different perspectives, including dimensions, measures, filters, and sorting. OLAP helps users identify and understand patterns, trends, and relationships within the 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 Recommended configurations.
OBKV
OBKV is a multi-model key-value (KV) product of OceanBase Database. It is primarily used for providing low-cost, large-scale storage for structured and semi-structured data, along with high access performance through simple operation interfaces. OBKV bypasses the SQL layer and directly utilizes OceanBase's distributed storage to build various multi-model KV forms. Between the distributed storage and multi-model forms, OBKV has a framework layer called TableAPI, which provides encapsulated storage and transaction call capabilities to the model layer.
For more information about the recommended configurations for this scenario, see Recommended configurations.
References
- For detailed information about parameters and variables, see Overview of parameters and system variables.
- For information about how to set parameters, see Set parameters.
- For information about how to set variables, see Set variables.