Skip to main content

Parameter Templates

Parameter templates are required by microservice customers. These customers run their business on a software as a service (SaaS) platform. Tenants in the same cluster may run the same business. However, tenant parameters must be configured each time a tenant is created. In a SaaS-based business scenario with a large number of tenants, the workload in configuring tenant parameters is heavy.

Other users also raise similar requirements. They hope that templates of recommended parameter settings can be provided for different business scenarios. After a business scenario is specified for a cluster or tenant, the system automatically tunes various parameters to adapt to the scenario.

To meet these requirements, OceanBase Database provides the parameter template feature. For a cluster or tenant created by using OceanBase Cloud Platform (OCP) or OceanBase Deployer (obd), parameters and their default settings are tuned to cater to business needs in different scenarios.

Background Information​

I have recently come into contact with some users of OceanBase Database Community Edition and found that their application scenarios are diverse. However, the default parameter/variable settings provided by OceanBase Database do not apply to all scenarios. The recommended parameter/variable settings vary based on the application scenario. For example, the default value of the ob_query_timeout variable is 10s, which is acceptable for simple online transaction processing (OLTP) scenarios but may not be suitable for online analytical processing (OLAP) business, especially for time-consuming complex queries.

To provide more suitable default parameter settings for clusters and tenants in different application scenarios, OceanBase Database provides the parameter template feature. I have tried this feature for a few days and here are my usage records for your reference.

I used OceanBase Database Community Edition V4.3.2.1 and OCP Community Edition V4.3.1 for testing. We recommend that you use OCP Community Edition V4.3.2 or later, which fixes some known bugs and provides comprehensive parameter template functionality.

Check the Configuration File for Parameter Templates​

In the OBServer source code of OceanBase Database, parameters and their default settings for various scenarios are maintained and output as an RPM package. When you upload the software package of OceanBase Database V4.3.0 or later to OCP, the configuration file in the software package is automatically parsed in the background of OCP and saved as a parameter template of the cluster or tenant.

image.png

It takes about 1 minute to parse the configuration file and save it to a certain meta table. If you cannot see the options of the parameter template on the OCP GUI after waiting for a long time, confirm whether OCP has finished parsing the parameter template configuration file. The procedure is as follows:

  1. Log in to the OCP console, choose Tenants > User Management, and copy the login connection string of the ocp_meta tenant.

image.png

  1. Log in to the ocp_meta tenant on the corresponding OBServer node by using the copied connection string.
[xiaofeng.lby@obvos-dev-d3 /home/xiaofeng.lby]
$mysql -h1.2.3.4 -P2881 -u root@ocp_meta -p YourPassword

Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MySQL connection id is 3221740061
Server version: 5.7.25 OceanBase_CE 4.2.1.2
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
  1. A scenario-based parameter template is saved in the background. You cannot directly see it on the parameter template page but you can confirm in the MetaDB whether it exists.
MySQL [(none)]> use meta_database;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed

-- View cluster-level parameter template types. Here is an example. You can delete limit 1 and then execute the statement.
MySQL [meta_database]> select * from meta_database.ob_cluster_parameter_template where `group` = 'scenario' limit 1 \G
*************************** 1. row ***************************
             id: 1001
    create_time: 2024-09-20 14:28:09
    update_time: 2024-09-20 14:28:09
           name: cluster parameter template for scenario HTAP, version 4.3.2.1-100000102024081217
     creator_id: 200
    modifier_id: 200
    description: cluster parameter template for scenario HTAP, version 4.3.2.1-100000102024081217
       built_in: 0
extra_data_json: {"fullVersion":"4.3.2.1-100000102024081217","scenario":"HTAP"}
          group: scenario
1 row in set (0.04 sec)

-- View tenant-level parameter template types. Here is an example. You can delete limit 1 and then execute the statement.
MySQL [meta_database]> select * from meta_database.ob_tenant_parameter_template where `group` = 'scenario' limit 1 \G
*************************** 1. row ***************************
             id: 1001
    create_time: 2024-09-20 14:28:09
    update_time: 2024-09-20 14:28:09
           name: tenant parameter template for scenario HTAP, version 4.3.2.1-100000102024081217
     creator_id: 200
    modifier_id: 200
    description: tenant parameter template for scenario HTAP, version 4.3.2.1-100000102024081217
compatible_type: ALL
       built_in: 0
extra_data_json: {"fullVersion":"4.3.2.1-100000102024081217","scenario":"HTAP"}
          group: scenario
1 row in set (0.04 sec)

Set a Cluster-level Parameter Template​

When you create a cluster of OceanBase Database V4.3.0 or later, you can select a parameter template based on the application scenario.

image.png

The procedure is simple. On the Create Cluster page of the OCP console, you can either use the default parameter settings or enable Parameter Settings to modify cluster parameters.

  • You can add and configure startup parameters one by one.
  • You can also click Parameter Template and select a parameter template. The system will automatically populate the parameters and their values from the template on the cluster parameter configuration page.

OceanBase Database V4.3.2.1 used for testing provides five built-in parameter templates, which are described in the following table.

TemplateDescription
Default Parameter Template for HTAPSuitable for hybrid transactional and analytical processing (HTAP) workloads. You can use it to quickly get insights from campaign operation data, fraud detection, and scenario-specific recommendations. This template applies to OceanBase Database V4.3.0 and later.
Default Parameter Template for OLAPSuitable for real-time data warehouse analytics. This template applies to OceanBase Database V4.3.0 and later.
Default Parameter Template for COMPLEX_OLTPSuitable for workloads such as banking and insurance systems. These workloads often involve complex join operations, complex subqueries, batch processing jobs compiled in PL, long-running transactions, and large transactions. Short-running queries are sometimes executed in parallel. This template applies to OceanBase Database V4.3.0 and later.
Default Parameter Template for KVSuitable for workloads involving a high throughput and are sensitive to latency, such as key-value workloads and wide-column workloads of an HBase database. This template applies to OceanBase Database V4.3.0 and later.
Default Parameter Template for OceanBase Database V2.2.77The template recommended for a production cluster of OceanBase Database V2.2.77.

Set a Tenant-level Parameter Template​

image.png

Log in to the OCP console and choose Tenants > Create Tenant. On the page that appears, enable Parameter Settings and configure the tenant parameters.

  • You can add and configure startup parameters one by one.
  • You can also click Parameter Template and select a parameter template. The system will automatically populate the parameters and their values from the template on the tenant parameter configuration page.

Solution to a Known Bug (Fixed in OCP Community Edition V4.3.2)​

When a user creates a tenant in OCP by using the Default Parameter Template for OLAP, OCP misjudges the types of some parameters because part of the metadata recorded by OCP is incorrect. As a result, the tenant fails to be created. This bug does not occur in cluster creation or when a tenant is created by using other parameter templates.

This bug has been fixed in OCP Community Edition V4.3.2. If you use the Default Parameter Template for OLAP to create a tenant in OCP of a version earlier than V4.3.2, you can temporarily delete the parameters without a value type, namely, parallel_degree_policy, _io_read_batch_size, and _io_read_redundant_limit_percentage.

After the tenant is created, choose Tenants > Parameter Management and manually configure these three parameters.

image.png

Performance Tests with Different Parameter Templates​

Typical production environments​

Our team member Junye has tested the parameter templates in different benchmarks. Currently, OceanBase Database Community Edition provides five typical production environments:

  • EXPRESS_OLTP: for Internet applications featuring simple CRUD statements, a large number of point queries, and high concurrency
  • COMPLEX_OLTP: for traditional industry applications featuring complex queries, a large number of PL queries, and batch processing jobs
  • OLAP: online analytical processing and data warehousing.
    • Typical load: import -> conversion -> query -> report generation
      • Lightweight:
        • Extract, load, transform (ELT) rather than extract, transform, load (ETL)
        • SQL used for data conversion and real-time queries, and materialized views used for real-time acceleration
        • Simple and lightweight dependencies, namely, no or a few external dependencies
    • Performance metric: response time, ranging from seconds to hours
    • Data size: 100 TB
    • Data model: star schema for multi-table joins and multidimensional ad-hoc queries on wide tables
    • Read/Write mode: more reads than writes, batch writes with a few updates, a few query types with a low query concurrency, and queries featuring wide-range scan
    • Typical benchmarks: TPC-DS, TPC-H, ClickBench, and Star Schema Benchmark (SSB)
    • Application scenarios: real-time warehousing, marketing analysis, aggregation analysis, and ad-hoc queries
  • HTAP: hybrid load processing with enhanced transaction processing (TP) capabilities
    • Real-time lightweight reports
      • Typical load: online transaction write -> batch processing job -> real-time report
      • Typical benchmarks: TPC-C + TPC-H, and Hybench
      • Data size: 10 TB
      • Performance metric: subsecond-level response time of an analytical query
      • Data model: basically designed in accordance with the relational model paradigm
      • Read/Write mode: heavy reads and writes with high read and write concurrency. Data is written in real time, including high-concurrency writes of transactions involving small amounts of data and batch writes of large transactions. Data reads include transactional short queries and analytical large queries.
      • Application scenarios: (a) BI reports, (b) substitute for the "database/table sharding + aggregated database" dual-database instance architecture, (c) ad-hoc queries, and (d) real-time risk control
    • Quasi-real-time decision analysis
      • Typical load: online transactions with a high concurrency and large-scale real-time data analysis
      • Data size: 100 TB
      • Performance metric: response time of an analytical query, ranging from subseconds to hours
      • Data model: basically designed in accordance with the relational model paradigm
      • Read/Write mode: heavy reads and writes with high read and write concurrency. Data is written in real time, including high-concurrency writes of transactions involving small amounts of data and batch writes of large transactions. Data reads include transactional short queries and analytical large queries, which can be separated on the application side. Analytical queries support old data.
      • Typical benchmarks: TPC-C + TPC-DS, and TPC-C + ClickBench
      • Application scenarios: (a) BI reports, (b) substitute for the "database/table sharding + aggregated database" dual-database instance architecture, and (c) ad-hoc queries
  • KV: applicable to OBKV HBase-compatible access and key-value table access, single-partition access, and no-SQL layer.

Default values for parameters in templates​

  • System variables: For more information, see GitHub.
  • Parameters: For more information, see GitHub.

Test environment​

Test versions​

  • OceanBase Database Community Edition: V4.3.2
  • OceanBase Database Proxy (ODP) Community Edition: V4.2.3
Hardware environment​
  • Three OBServer nodes are deployed on ecs.r7.8xlarge servers, each with 32 CPU cores and 256 GB of memory. The system disk is used as the system log disk, while two PL1 ESSDs are mounted to store clogs and data, respectively.
  • ODP is deployed on a separate ecs.c7.16xlarge server with 64 CPU cores and 128 GB of memory.
Operating system​

The operating system is CentOS 7.9 64-bit.

echo "vm.max_map_count=655360" >> /etc/sysctl.conf; sysctl -p (obd startup check items)
sudo sysctl -w kernel.sched_migration_cost_ns=0 (optimization based on kernel parameters of ApsaraDB for OceanBase)
Tenant specifications​

28 CPU cores, 180 GB of memory, three full-featured replicas, and primary_zone set to RANDOM

## Valid values of scenario in the command are express_oltp, complex_oltp, olap, htap, and kv.
obd cluster tenant create perf --max-cpu=28 --memory-size=180G -n mysql_tenant -o ${scenario}
Deployment configuration file​
oceanbase-ce:
  version: 4.3.2.0
  servers:
    - name: server1
      ip: omitted
    - name: server2
      ip: omitted
    - name: server3
      ip: omitted
  global:
    scenario: ${scenario}
    home_path: /root/observer
    data_dir: /data/1/storage
    redo_dir: /data/2/redo
    devname: eth0
    memory_limit: 240G
    log_disk_size: 700G
    datafile_disk_percentage: 93
    root_password: 123456
    mysql_port: 2881
    rpc_port: 2882
  server1:
    zone: zone1
  server2:
    zone: zone2
  server3:
    zone: zone3
obproxy-ce:
  version: 4.2.3.0
  depends:
    - oceanbase-ce
  servers:
    - omitted
  global:
    listen_port: 2886 ## External port. The default value is 2883.
    home_path: /root/obproxy
    enable_cluster_checkout: false
    skip_proxy_sys_private_check: true
    enable_strict_kernel_release: false

Tune parameters​

In this section, performance data is tested based on the tuned basic workload parameters and default parameter settings for different types of tenants.

Tune basic workload parameters​

Sysbench

ALTER system SET enable_sql_audit=false;
ALTER system SET enable_perf_event=false;
ALTER system SET syslog_level='PERF';
alter system set enable_record_trace_log=false;

TPC-C

#proxy
ALTER proxyconfig SET proxy_mem_limited='4G';
ALTER proxyconfig set enable_compression_protocol=false;

#sys
ALTER system SET enable_sql_audit=false;
select sleep(5);
ALTER system SET enable_perf_event=false;
ALTER system SET syslog_level='PERF';
alter system set enable_record_trace_log=false;

TPC-H

#sys
ALTER SYSTEM flush plan cache GLOBAL;
ALTER system SET enable_sql_audit=false;
select sleep(5);
ALTER system SET enable_perf_event=false;
ALTER system SET syslog_level='PERF';
alter system set enable_record_trace_log=false;

#Test tenant
SET GLOBAL ob_sql_work_area_percentage = 80;
SET GLOBAL ob_query_timeout = 36000000000;
SET GLOBAL ob_trx_timeout = 36000000000;
SET GLOBAL max_allowed_packet = 67108864;
## parallel_servers_target = max_cpu * server_num * 8
SET GLOBAL parallel_servers_target = 624;

TPC-DS

#sys
ALTER SYSTEM flush plan cache GLOBAL;
ALTER system SET enable_sql_audit=false;
select sleep(5);
ALTER system SET enable_perf_event=false;
ALTER system SET syslog_level='PERF';
alter system set enable_record_trace_log=false;

#Test tenant
SET GLOBAL ob_sql_work_area_percentage = 80;
SET GLOBAL ob_query_timeout = 36000000000;
SET GLOBAL ob_trx_timeout = 36000000000;
SET GLOBAL max_allowed_packet = 67108864;
## parallel_servers_target = max_cpu * server_num * 8
SET GLOBAL parallel_servers_target = 624;

Test data​

Sysbench​

Parameter tuning

ALTER system SET enable_sql_audit=false;
ALTER system SET enable_perf_event=false;
ALTER system SET syslog_level='PERF';
alter system set enable_record_trace_log=false;

Test command

The native Sysbench benchmark process encapsulated by obd is used. The ob-sysbench used by obd depends on LibOBClient. You need to run export ENABLE_PROTOCOL_OB20=0 to disable the OceanBase 2.0 protocol to keep consistent with the native Sysbench benchmark.

obd test sysbench rn --tenant=perf --script-name=xxx.lua --table-size=1000000 --threads=xx  --report-interval=1 --rand-type=uniform --time=30 --db-ps-mode=disable

Test data (QPS/95% RT)

POINT_SELECT performance

ThreadsEXPRESS_OLTPCOMPLEX_OLTPOLAPHTAPKV
32163457.60/0.22162747.70/0.22161428.80/0.23162948.95/0.20163204.29/0.20
64296206.41/0.25291823.36/0.26291583.48/0.26293622.63/0.25295541.97/0.25
128505203.80/0.30493859.95/0.31492135.78/0.31498132.19/0.31505266.56/0.30
256798005.94/0.45794547.97/0.47803165.10/0.49797304.31/0.45794627.82/0.45
5121039286.05/0.901023822.11/1.141022666.33/1.121032713.76/0.901016045.20/0.92
10241013992.61/2.391011295.14/2.39997362.00/2.571004848.34/2.48990136.68/2.52

READ_ONLY performance

ThreadsEXPRESS_OLTPCOMPLEX_OLTPOLAPHTAPKV
32134791.19/4.10136145.15/3.97137486.55/3.96137327.53/3.95137750.08/3.96
64244754.37/4.49244093.17/4.57244641.01/4.57244586.46/4.57247914.45/4.49
128416929.45/5.37420143.73/5.47419772.35/5.28420445.05/5.28421381.09/5.28
256613453.13/7.56611436.43/8.28603989.96/8.28610998.14/7.43607015.73/8.13
512725364.76/16.12738362.91/17.65736059.64/15.83720899.31/16.12693449.90/26.20
1024715777.22/41.10707831.35/42.61697077.19/44.17706809.11/42.61699619.03/44.83

WRITE_ONLY performance

ThreadsEXPRESS_OLTPCOMPLEX_OLTPOLAPHTAPKV
3250914.06/5.0052894.62/4.9150589.47/5.6752088.46/4.7454033.87/4.41
6490119.99/5.4793447.67/5.3790202.65/5.3790264.56/5.5794874.07/5.00
128164488.33/5.77166099.69/5.57159493.96/5.99159005.24/6.09162650.65/5.57
256242240.38/8.13241749.01/8.43232320.85/8.43230522.31/8.74238971.17/7.84
512304060.67/13.70306416.65/13.70299155.86/13.70289147.63/13.95301695.38/13.22
1024345068.37/23.52348929.05/26.20306096.92/29.72327905.15/27.17313276.26/30.81

READ_WRITE performance

ThreadsEXPRESS_OLTPCOMPLEX_OLTPOLAPHTAPKV
3290881.38/7.8488141.94/8.2888216.59/8.5889948.44/7.9890592.37/7.98
64159748.46/8.90160695.31/9.06157714.41/10.09157230.31/9.39161391.32/8.90
128273142.95/10.46275431.02/10.27272648.28/10.27269700.79/11.24275952.12/10.46
256391348.85/15.27402154.83/15.00382679.53/16.71383447.47/15.27405787.34/14.46
512465031.62/28.67462574.18/33.72466465.96/26.20461249.29/27.66464724.24/27.66
1024525924.96/52.89535977.26/48.34510540.58/58.92522066.61/51.02521969.84/51.94

TPC-C​

Parameter tuning

#proxy
ALTER proxyconfig SET proxy_mem_limited='4G';
ALTER proxyconfig set enable_compression_protocol=false;

#sys
ALTER system SET enable_sql_audit=false;
select sleep(5);
ALTER system SET enable_perf_event=false;
ALTER system SET syslog_level='PERF';
alter system set enable_record_trace_log=false;

Test command

The TPC-C benchmark process encapsulated by obd is used. For more information, see Run the TPC-C benchmark on OceanBase Database.

obd test tpcc rn --tenant=perf --tmp-dir=/data/2/tpcc  --warehouses=1000 --load-workers=40 --terminals=800 --run-mins=5 -v -O 2

Test data

express_oltpcomplex_oltpolaphtapkv
tpmC (NewOrders)292204.95302608.69264422.69294316.6286362.9
tpmTOTAL648918.9672866.36587580.74654271.82636369.93
Transaction Count32463243366013293916632725143183132

TPC-H​

Parameter tuning

#sys
ALTER SYSTEM flush plan cache GLOBAL;
ALTER system SET enable_sql_audit=false;
select sleep(5);
ALTER system SET enable_perf_event=false;
ALTER system SET syslog_level='PERF';
alter system set enable_record_trace_log=false;

#Test tenant
SET GLOBAL ob_sql_work_area_percentage = 80;
SET GLOBAL ob_query_timeout = 36000000000;
SET GLOBAL ob_trx_timeout = 36000000000;
SET GLOBAL max_allowed_packet = 67108864;
## parallel_servers_target = max_cpu * server_num * 8
SET GLOBAL parallel_servers_target = 624;

Test command

The TPC-H benchmark process encapsulated by obd is used. For more information, see Run the TPC-H benchmark on OceanBase Database.

obd test tpch rn --user=root --test-server=server1 --tmp-dir=/data/2/ob   --tenant=perf --remote-tbl-dir=/home/admin -s 100

Test data (columnstore tables used)

express_oltpcomplex_oltpolaphtapkv
Q132.33s9.86s1.83s3.03s1.90s
Q21.42s0.52s0.22s0.26s0.22s
Q37.79s2.58s0.52s0.91s0.54s
Q49.55s3.01s0.27s0.66s0.27s
Q515.77s4.59s0.73s1.29s0.70s
Q60.25s0.11s0.06s0.06s0.05s
Q79.76s3.65s1.19s1.76s1.18s
Q85.72s1.85s0.39s0.61s0.38s
Q925.26s8.93s1.88s3.28s1.88s
Q103.96s1.74s0.46s0.75s0.46s
Q112.01s0.61s0.14s0.21s0.13s
Q126.00s1.89s0.33s0.66s0.39s
Q138.40s3.43s1.64s1.94s1.64s
Q140.99s0.45s0.19s0.25s0.19s
Q151.29s0.64s0.31s0.34s0.31s
Q162.69s1.07s0.53s0.61s0.51s
Q173.85s1.15s0.21s0.31s0.20s
Q1817.53s5.51s1.33s1.96s1.27s
Q191.49s0.60s0.24s0.31s0.23s
Q206.02s2.38s1.33s1.33s1.30s
Q2126.01s9.11s2.70s3.60s2.74s
Q226.01s2.23s0.79s1.00s0.78s
Total194.10s65.91s17.26s25.13s17.28s

TPC-DS​

Parameter tuning

#sys
ALTER SYSTEM flush plan cache GLOBAL;
ALTER system SET enable_sql_audit=false;
select sleep(5);
ALTER system SET enable_perf_event=false;
ALTER system SET syslog_level='PERF';
alter system set enable_record_trace_log=false;

#Test tenant
SET GLOBAL ob_sql_work_area_percentage = 80;
SET GLOBAL ob_query_timeout = 36000000000;
SET GLOBAL ob_trx_timeout = 36000000000;
SET GLOBAL max_allowed_packet = 67108864;
## parallel_servers_target = max_cpu * server_num * 8
SET GLOBAL parallel_servers_target = 624;

Test command

The test data volume is 100 GB. For the test process, see Run the TPC-DS benchmark on OceanBase Database.

Test data (columnstore tables used)

Queryexpress_oltpcomplex_oltpolaphtapkv
Q10.620.330.210.210.20
Q210.193.290.991.260.99
Q30.200.130.110.110.11
Q436.4217.8911.2911.9011.39
Q53.951.790.981.111.00
Q60.550.310.220.230.32
Q70.810.380.190.210.29
Q80.550.320.240.240.22
Q92.150.950.470.510.48
Q101.810.850.520.540.50
Q1122.0910.947.097.357.13
Q120.470.290.220.240.23
Q130.530.270.180.190.19
Q1481.1926.907.8610.408.01
Q150.710.430.380.390.39
Q165.181.740.570.730.57
Q171.260.640.390.440.41
Q180.710.390.260.280.37
Q190.300.200.150.160.16
Q200.390.260.190.210.20
Q210.990.390.160.200.17
Q224.932.141.121.261.14
Q2392.3734.4213.2716.4113.41
Q243.471.550.840.930.85
Q251.140.590.410.430.40
Q260.490.260.160.190.16
Q271.140.540.310.330.31
Q281.370.950.830.840.86
Q293.941.340.460.560.45
Q300.400.270.220.220.22
Q312.371.080.600.670.59
Q320.120.110.100.100.10
Q331.210.870.630.660.62
Q342.220.770.220.290.20
Q353.571.510.760.850.72
Q361.980.850.290.400.29
Q370.520.320.230.240.23
Q387.002.991.501.701.52
Q392.981.310.720.810.71
Q400.290.180.150.150.14
Q410.040.040.040.030.04
Q420.180.120.100.100.10
Q433.891.430.470.600.47
Q440.500.450.440.460.45
Q450.470.370.350.360.35
Q460.970.460.280.300.27
Q475.122.110.991.110.98
Q480.540.290.170.180.16
Q491.250.960.840.850.82
Q508.072.360.440.650.44
Q5122.357.022.813.042.83
Q520.170.130.100.100.10
Q531.560.520.170.200.16
Q542.240.970.540.570.52
Q550.140.110.100.100.10
Q560.670.610.600.590.57
Q572.881.290.660.740.67
Q581.150.850.690.690.68
Q5918.736.562.102.642.04
Q601.160.850.670.690.66
Q610.410.330.290.290.29
Q623.001.150.370.470.36
Q631.570.520.160.200.16
Q646.743.011.451.711.42
Q654.181.660.730.860.70
Q661.000.610.380.400.37
Q6721.5613.4910.4310.2810.44
Q680.370.260.220.230.22
Q691.230.660.480.500.47
Q705.392.261.151.281.16
Q711.200.670.420.450.40
Q7222.3914.6810.4011.0910.44
Q730.630.320.170.200.17
Q7414.226.833.683.933.59
Q756.722.801.421.551.39
Q760.390.380.390.380.38
Q771.390.880.730.720.70
Q7814.465.912.573.002.56
Q792.661.170.480.560.48
Q802.941.500.971.000.95
Q810.630.290.160.180.16
Q820.780.450.320.330.37
Q831.140.750.580.590.58
Q840.580.280.180.180.18
Q850.710.450.360.360.36
Q861.140.560.340.390.35
Q877.293.041.591.721.57
Q881.830.780.290.360.29
Q891.780.720.230.320.24
Q900.440.220.140.150.14
Q910.140.110.100.100.10
Q920.110.100.100.100.10
Q937.682.240.470.640.47
Q942.741.080.490.560.49
Q9539.7518.006.978.236.72
Q962.430.780.200.260.20
Q977.342.641.011.221.04
Q980.640.420.310.330.31
Q996.002.160.680.800.65
Total570.64s242.76s119.88s134.26s119.98s

Summary​

After a tenant is created by using a parameter template, the benchmark results for the corresponding business scenario show that the performance is significantly improved. The parameter template feature will be gradually popularized among OceanBase Database users. We recommend that you have a try.

Loading...