TiDB Sysbench Performance Test Report -- v5.4.0 vs. v5.3.0

Test overview

This test aims at comparing the Sysbench performance of TiDB v5.4.0 and TiDB v5.3.0 in the Online Transactional Processing (OLTP) scenario. The results show that performance of v5.4.0 is improved by 2.59% ~ 4.85% in the write-heavy workload.

Test environment (AWS EC2)

Hardware configuration

Service typeEC2 typeInstance count
PDm5.xlarge3
TiKVi3.4xlarge3
TiDBc5.4xlarge3
Sysbenchc5.9xlarge1

Software version

Service typeSoftware version
PDv5.3.0 and v5.4.0
TiDBv5.3.0 and v5.4.0
TiKVv5.3.0 and v5.4.0
Sysbench1.1.0-ead2689

Parameter configuration

TiDB v5.4.0 and TiDB v5.3.0 use the same configuration.

TiDB parameter configuration

log.level: "error"
performance.max-procs: 20
prepared-plan-cache.enabled: true
tikv-client.max-batch-wait-time: 2000000

TiKV parameter configuration

storage.scheduler-worker-pool-size: 5
raftstore.store-pool-size: 3
raftstore.apply-pool-size: 3
rocksdb.max-background-jobs: 8
raftdb.max-background-jobs: 4
raftdb.allow-concurrent-memtable-write: true
server.grpc-concurrency: 6
readpool.unified.min-thread-count: 5
readpool.unified.max-thread-count: 20
readpool.storage.normal-concurrency: 10
pessimistic-txn.pipelined: true

TiDB global variable configuration

set global tidb_hashagg_final_concurrency=1;
set global tidb_hashagg_partial_concurrency=1;
set global tidb_enable_async_commit = 1;
set global tidb_enable_1pc = 1;
set global tidb_guarantee_linearizability = 0;
set global tidb_enable_clustered_index = 1;

HAProxy configuration - haproxy.cfg

For more details about how to use HAProxy on TiDB, see Best Practices for Using HAProxy in TiDB.

global                                     # Global configuration.
   chroot      /var/lib/haproxy            # Changes the current directory and sets superuser privileges for the startup process to improve security.
   pidfile     /var/run/haproxy.pid        # Writes the PIDs of HAProxy processes into this file.
   maxconn     4000                        # The maximum number of concurrent connections for a single HAProxy process.
   user        haproxy                     # The same with the UID parameter.
   group       haproxy                     # The same with the GID parameter. A dedicated user group is recommended.
   nbproc      64                          # The number of processes created when going daemon. When starting multiple processes to forward requests, ensure that the value is large enough so that HAProxy does not block processes.
   daemon                                  # Makes the process fork into background. It is equivalent to the command line "-D" argument. It can be disabled by the command line "-db" argument.
defaults                                   # Default configuration.
   log global                              # Inherits the settings of the global configuration.
   retries 2                               # The maximum number of retries to connect to an upstream server. If the number of connection attempts exceeds the value, the backend server is considered unavailable.
   timeout connect  2s                     # The maximum time to wait for a connection attempt to a backend server to succeed. It should be set to a shorter time if the server is located on the same LAN as HAProxy.
   timeout client 30000s                   # The maximum inactivity time on the client side.
   timeout server 30000s                   # The maximum inactivity time on the server side.
listen tidb-cluster                        # Database load balancing.
   bind 0.0.0.0:3390                       # The Floating IP address and listening port.
   mode tcp                                # HAProxy uses layer 4, the transport layer.
   balance roundrobin                      # The server with the fewest connections receives the connection. "leastconn" is recommended where long sessions are expected, such as LDAP, SQL and TSE, rather than protocols using short sessions, such as HTTP. The algorithm is dynamic, which means that server weights might be adjusted on the fly for slow starts for instance.
   server tidb-1 10.9.18.229:4000 check inter 2000 rise 2 fall 3       # Detects port 4000 at a frequency of once every 2000 milliseconds. If it is detected as successful twice, the server is considered available; if it is detected as failed three times, the server is considered unavailable.
   server tidb-2 10.9.39.208:4000 check inter 2000 rise 2 fall 3
   server tidb-3 10.9.64.166:4000 check inter 2000 rise 2 fall 3

Test plan

  1. Deploy TiDB v5.4.0 and v5.3.0 using TiUP.
  2. Use Sysbench to import 16 tables, each table with 10 million rows of data.
  3. Execute the analyze table statement on each table.
  4. Back up the data used for restore before different concurrency tests, which ensures data consistency for each test.
  5. Start the Sysbench client to perform the point_select, read_write, update_index, and update_non_index tests. Perform stress tests on TiDB via HAProxy. For each concurrency under each workload, the test takes 20 minutes.
  6. After each type of test is completed, stop the cluster, overwrite the cluster with the backup data in step 4, and restart the cluster.

Prepare test data

Run the following command to prepare the test data:

sysbench oltp_common \
    --threads=16 \
    --rand-type=uniform \
    --db-driver=mysql \
    --mysql-db=sbtest \
    --mysql-host=$aws_nlb_host \
    --mysql-port=$aws_nlb_port \
    --mysql-user=root \
    --mysql-password=password \
    prepare --tables=16 --table-size=10000000

Perform the test

Run the following command to perform the test:

sysbench $testname \
    --threads=$threads \
    --time=1200 \
    --report-interval=1 \
    --rand-type=uniform \
    --db-driver=mysql \
    --mysql-db=sbtest \
    --mysql-host=$aws_nlb_host \
    --mysql-port=$aws_nlb_port \
    run --tables=16 --table-size=10000000

Test results

Point Select performance

Threadsv5.3.0 TPSv5.4.0 TPSv5.3.0 95% latency (ms)v5.4.0 95% latency (ms)TPS improvement (%)
300266041.84264345.731.962.07-0.64
600351782.71348715.983.433.49-0.87
900386553.31399777.115.094.743.42

Compared with v5.3.0, the Point Select performance of v5.4.0 is slightly improved by 0.64%.

Point Select

Update Non-index performance

Threadsv5.3.0 TPSv5.4.0 TPSv5.3.0 95% latency (ms)v5.4.0 95% latency (ms)TPS improvement (%)
30040804.3141187.111.8711.870.94
60051239.453172.0320.7419.653.77
90057897.5659666.827.6627.663.06

Compared with v5.3.0, the Update Non-index performance of v5.4.0 is improved by 2.59%.

Update Non-index

Update Index performance

Threadsv5.3.0 TPSv5.4.0 TPSv5.3.0 95% latency (ms)v5.4.0 95% latency (ms)TPS improvement (%)
30017737.8218716.526.224.835.52
60021614.3922670.7444.9842.614.89
90023933.724922.0562.1961.084.13

Compared with v5.3.0, the Update Index performance of v5.4.0 is improved by 4.85%.

Update Index

Read Write performance

Threadsv5.3.0 TPSv5.4.0 TPSv5.3.0 95% latency (ms)v5.4.0 95% latency (ms)TPS improvement (%)
3003810.783929.29108.68106.753.11
6004514.284684.64193.38186.543.77
9004842.494988.49282.25277.213.01

Compared with v5.3.0, the Read Write performance of v5.4.0 is improved by 3.30%.

Read Write

Was this page helpful?