TPC-C test report of OceanBase Database

This topic details the TPC-C test environment, methods, and results.

Test environment

The tests use Alibaba Cloud ECS as the deployment platform.

• Hardware configuration

  Service type	ECS type	Number of instances	CPU cores	Memory
  OceanBase Database	ecs.g7.8xlarge	3	32	128 GB Each has a 300 GB system disk, plus two 400 GB cloud disks for clog and data (PL1 performance).
  OceanBase Database Proxy (ODP), Benchmark SQL	ecs.c7.16xlarge	1	32	128 GB

• Software version

  Service type	Software version
  OceanBase Database	Enterprise Edition: OceanBase 4.3.5.4 Community Edition: OceanBase_CE 4.3.5.4
  ODP	OceanBase 4.3.1
  Benchmark SQL	Benchmark SQL V5.0
  JDBC	mysql-connector-java-5.1.47
  OS	CentOS Linux release 7.9.2009 (Core)

• Tenant specifications

  obd cluster tenant create obperf -n tpcc_tenant --max-cpu=28 --memory-size=180G -–zone-list=zone1,zone2,zone3 -–primary-zone=RANDOM  --locality=F@zone1,F@zone2,F@zone3 --charset=utf8 -s 'ob_tcp_invited_nodes="%"' --optimize=htap
  

  Note

  In this example, --optimize=htap is set as the default workload type. For production environments, select the workload type that best matches your actual cluster configuration.

Test methods

1. Deploy the OceanBase cluster by using OceanBase Deployer (obd). Deploy ODP and TPC-C separately on one machine to avoid client pressure from becoming a performance bottleneck.

2. Deploy three OceanBase nodes in a 1:1:1 configuration. After deployment, create a dedicated tenant and user for the TPC-C test (the sys tenant is reserved for cluster management and cannot be used for testing). Set the tenant's primary_zone to RANDOM.

3. For more information about how to perform the TPC-C test, see Run the TPC-C benchmark test on OceanBase Database.

Test specifications

warehouses=1000
loadWorkers=40
terminals=1000
runMins=5
newOrderWeight=45
paymentWeight=43
orderStatusWeight=4
deliveryWeight=4
stockLevelWeight=4

Test results

In this test, the cluster workload type and the tenant parameter template are consistent. All tests run with a concurrency level of 96.