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

Scenario 1: All the data that you query is hit in the cache.

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

(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 2371.56 118.58
2 4 1,200 2,000 8 12544.18 627.21
2 8 2,000 4,000 8 13130.27 656.51
4 8 2,000 5,000 16 39674.97 1983.75
4 16 4,000 7,000 16 39766.67 1988.33
8 16 4,000 8,000 32 64750.34 3237.52
8 32 8,000 12,000 32 66143.9 3307.2
16 64 16,000 14,000 64 102495.1 5124.76

Scenario 2: Only some data that you query is hit in the cache, and the RDS instance needs to read and write data to disks 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

(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 1603.88 80.19
2 8 2,000 4,000 64 3591.69 179.58
4 8 2,000 5,000 64 4491.16 224.56
4 16 4,000 7,000 64 8155.33 407.77
8 16 4,000 8,000 64 9320.91 466.05
8 32 8,000 12,000 64 29902.55 1495.13
16 64 16,000 14,000 64 98221.43 4911.07