This topic describes the performance test results of a general-purpose ApsaraDB for RDS instance that runs MySQL 8.0.

Note The performance test results are for reference only. For more information about how to use an ApsaraDB RDS instance that runs MySQL 8.0, see Troubleshoot slow SQL statements on an ApsaraDB RDS for MySQL instance.

Scenario 1: Cache-based queries

All data can be read to the cache for queries.

Set the table_size parameter to 25000 and the tables parameter to 250 in SysBench.

Scenario 1 based on ApsaraDB RDS for MySQL 8.0
CPU

(number of cores)

Memory capacity

(GB)

Maximum number of connections IOPS Number of SysBench threads SysBench QPS SysBench TPS
1 1 300 600 8 679.52 33.98
1 2 600 1,000 8 2,371.56 118.58
2 4 1,200 2,000 8 12,544.18 627.21
2 8 2,000 4,000 8 13,130.27 656.51
4 8 2,000 5,000 16 39,674.97 1,983.75
4 16 4,000 7,000 16 39,766.67 1,988.33
8 16 4,000 8,000 32 64,750.34 3,237.52
8 32 8,000 12,000 32 66,143.9 3,307.2
16 64 16,000 14,000 64 102,495.1 5,124.76

Scenario 2: Disk I/O-based queries

Only part of the data is read to the cache. The RDS instance needs to read and write data to the disk and update the cache to complete queries.

Set the table_size parameter to 800000 and the tables parameter to 150 in SysBench.

Scenario 2 based on ApsaraDB RDS for MySQL 8.0
CPU

(number of cores)

Memory capacity

(GB)

Maximum number of connections IOPS Number of SysBench threads SysBench QPS SysBench TPS
1 1 300 600 64 446.82 22.34
1 2 600 1,000 64 759.46 37.97
2 4 1,200 2,000 64 1,603.88 80.19
2 8 2,000 4,000 64 3,591.69 179.58
4 8 2,000 5,000 64 4,491.16 224.56
4 16 4,000 7,000 64 8,155.33 407.77
8 16 4,000 8,000 64 9,320.91 466.05
8 32 8,000 12,000 64 29,902.55 1,495.13
16 64 16,000 14,000 64 98,221.43 4,911.07