This topic describes the key parameters and differences among the parameter templates for tenant creation.
Parameter template configurations are available only for newly created tenants in OceanBase V4.3.3 and later.
Background information
ApsaraDB for OceanBase lets you select different parameter templates when you create a tenant. This helps you quickly configure the tenant for a specific business scenario to achieve optimal performance.
The following parameter templates are supported:
Online Transactional Processing (OLTP) simple transaction (default): Suitable for core systems such as online order processing and payment systems. It is also ideal for Internet businesses that primarily handle high-concurrency point queries. The SQL statements executed are simple and require fast responses.
OLTP complex transaction: Suitable for online transaction systems that involve complex transactions. These scenarios include complex join calculations, subqueries, and batch jobs written in PL. They may involve long-running or large transactions. If the cluster instance is dedicated to OLTP workloads, you can optimize the large query policy by changing the
large_query_thresholdcluster parameter from the default 600 s to 5 s.Hybrid Transactional and Analytical Processing (HTAP) hybrid workload: Suitable for workloads that run both transactions and online analytics. This template provides OLTP capabilities and uses a vectorized engine to improve computing performance for online analytics scenarios.
Online Analytical Processing (OLAP) online analysis: Suitable for real-time data warehouse scenarios. By default, tables are created in a column-store format. This template uses a more optimized vectorized engine to improve computing performance for complex analysis scenarios. If the cluster instance is dedicated to OLAP analysis, you can optimize the system variables and cluster parameters. For example, you can enable adaptive parallel computing, optimize memory space for SQL sorting, configure SQL and transaction timeout settings, and set the large query policy. In addition, you should set the tenant character set to
utf8mb4_bin.
Parameter template comparison
Parameter type | Parameter name | OLTP simple transaction | OLTP complex transaction | HTAP hybrid workload | OLAP online analysis |
Cluster parameter | large_query_threshold | 5s | 600s | 600s | 0 ms (large query disabled) |
trace_log_slow_query_watermark | 1s | 1s | 1s | 7 days | |
Tenant parameter | _rowsets_max_rows | 1 | 4 | 32 | 256 |
log_transport_compress_all | True | True | True | False | |
default_table_store_format | Row store | Row store | Row store | Column store | |
_io_read_batch_size | 0 K | 0 K | 0 KB | 128 KB | |
_io_read_redundant_limit_percentage | 0 | 0 | 0 | 50 | |
System variable | ob_query_timeout | 10s | 10s | 10s | 604,800,000,000 (7 days) |
ob_trx_timeout | 1 day | 1 day | 1 day | 604,800,000,000 (7 days) | |
parallel_degree_policy | MANUAL | MANUAL | MANUAL | AUTO | |
parallel_min_scan_time_threshold | 1s | 1s | 1s | 10ms | |
ob_sql_work_area_percentage | 5% | 5% | 5% | 30% | |
collation_server | utf8mb4_general_ci | utf8mb4_general_ci | utf8mb4_general_ci | utf8mb4_bin | |
collation_connection | utf8mb4_bin |