Help Center/ GaussDB/ Performance White Paper/ Test Data
Updated on 2024-11-11 GMT+08:00
View PDF
Share

Test Data

About IOPS

The input/output operations per second (IOPS) supported by GaussDB depends on the I/O performance of Elastic Volume Service (EVS) disks. For details, see Disk Types and Performance in the EVS Service Overview.

Test Data

  1. Instance type: distributed and centralized
  2. Instance specifications: 16 vCPUs | 128 GB and 32 vCPUs | 256 GB
  3. Cluster scale: 3 CNs, 3 shards, and 3 replicas for a distributed instance; 1 primary node and 2 standby nodes for a centralized instance
  4. Data volume: 1,000 warehouses
  5. Stress test duration: 30 minutes (5 minutes for warm-up)
Table 1 Performance data

Instance Type

Deployment Model

Instance Specifications

Concurrent Requests

tpmC

Centralized

HA (1 primary + 2 standby)

16 vCPUs | 128 GB

256

70,057

32 vCPUs | 256 GB

384

132,196

Distributed

Independent

16 vCPUs | 128 GB

1,024

466,930

32 vCPUs | 256 GB

2,048

658,805

Test Metrics

According to the Transaction Processing Performance Council (TPC), the throughput metric, tpmC, describes the number of new transactions processed per minute while the system is performing four types of transactions: payment operations, order status queries, deliveries, and stock status queries. The response time of all transactions and the proportion of each type of transactions must meet the requirements of the TPC-C test specifications. In this case, the larger the tpmC value is, the higher the online transaction processing (OLTP) capability of the system is.