This document describes the performance test results of a general TencentDB for MySQL 5.6 instance.
Scenario 1: Full Cache
In the full cache scenario, as all data can be put into the cache, the disk doesn't need to be read and written to update the cache during queries.
CPU
(Core)
Memory
(MB)
Concurrency
Data Volume/Table
Total Tables
SysBench TPS
SysBench QPS
avg_lat
1
1000
8
25000
150
577.97
11559.4
13.84
1
2000
8
25000
150
550.21
11004.3
14.54
2
4000
16
25000
150
1190.41
23808.1
13.44
4
8000
32
25000
150
2307.1
46142
13.87
4
16000
32
25000
150
2229.8
44596.1
14.35
8
16000
64
25000
150
3771.25
75425
16.97
8
32000
64
25000
150
3909.36
78187.1
16.37
16
32000
128
25000
150
6102.35
122047
20.97
16
64000
128
25000
150
6788.83
135777
18.85
16
96000
128
25000
150
6771.81
135436
18.9
16
128000
128
25000
150
7039.65
140793
18.18
Scenario 2: Disk I/O
In the disk I/O scenario, as only part of the data can be put into the cache, the disk needs to be read and written to update the cache during queries.
