Test Results for Full Cache
Last updated:2025-12-25 10:46:59
This document introduces the performance test results for general TDSQL-C for MySQL clusters in read-only, mixed read-write, and write-only scenarios where the data set characteristic is full cache.
Definition of Full Cache
The full cache scenarios refer to the situations where all data can be stored in the cache, and disk read and write operations are not required during queries to update the cache.
Test Scenarios and Read Types for Full Cache
Data Set Characteristic | Test Scenario | Read Type |
Full cache | Read-only | range select |
| | point select |
| Mixed read-write | range select |
| | point select |
| Write-only | - |
Test Results for Full Cache
Scenario 1: Read-Only (range select)
Specifications | Concurrency | Data Volume of a Single Table (table_size) | Total Number of Tables (tables) | TPS | QPS |
2 cores and 4 GB | 64 | 25000 | 250 | 3285.91 | 44613.74 |
4 cores and 8 GB | 256 | 25000 | 250 | 4285.39 | 58183.91 |
8 cores and 16 GB | 128 | 25000 | 250 | 6612.13 | 89774.81 |
8 cores and 32 GB | 64 | 25000 | 250 | 6624.26 | 89939.51 |
8 cores and 64 GB | 256 | 25000 | 250 | 7781.48 | 105651.42 |
16 cores and 64 GB | 128 | 25000 | 250 | 12692.22 | 172325.85 |
16 cores and 96 GB | 64 | 25000 | 250 | 12634.57 | 171543.18 |
16 cores and 128 GB | 128 | 25000 | 250 | 12683.51 | 172207.71 |
24 cores and 144 GB | 128 | 25000 | 250 | 18676.46 | 253575.68 |
32 cores and 128 GB | 128 | 25000 | 250 | 22790.74 | 309436.4 |
32 cores and 256 GB | 128 | 25000 | 250 | 22790.03 | 309426.71 |
64 cores and 256 GB | 512 | 25000 | 250 | 37885.38 | 514380.66 |
64 cores and 512 GB | 512 | 25000 | 250 | 37886.83 | 514400.36 |
88 cores and 710 GB | 32 | 25000 | 250 | 69542.04 | 944192.16 |
Scenario 2: Read-Only (point select)
Specifications | Concurrency | Data Volume of a Single Table (table_size) | Total Number of Tables (tables) | TPS | QPS |
2 cores and 4 GB | 64 | 25000 | 250 | 6755.38 | 70427.77 |
4 cores and 8 GB | 64 | 25000 | 250 | 9426.6 | 98276.43 |
8 cores and 16 GB | 64 | 25000 | 250 | 17670.01 | 184217.54 |
8 cores and 32 GB | 128 | 25000 | 250 | 17768.06 | 185239.75 |
8 cores and 64 GB | 256 | 25000 | 250 | 18089.73 | 188593.28 |
16 cores and 64 GB | 128 | 25000 | 250 | 34275.83 | 357340.39 |
16 cores and 96 GB | 128 | 25000 | 250 | 34466.73 | 359330.67 |
16 cores and 128 GB | 128 | 25000 | 250 | 34423.7 | 358882.04 |
24 cores and 144 GB | 256 | 25000 | 250 | 47890.53 | 499279.58 |
32 cores and 128 GB | 256 | 25000 | 250 | 62677.71 | 653442.34 |
32 cores and 256 GB | 256 | 25000 | 250 | 63552.76 | 662565.13 |
64 cores and 256 GB | 512 | 25000 | 250 | 89817.99 | 936391.58 |
64 cores and 512 GB | 512 | 25000 | 250 | 94144.71 | 981499.52 |
88 cores and 710 GB | 1024 | 25000 | 250 | 149084.38 | 1554269.37 |
Scenario 3: Mixed Read-Write (range select)
Specifications | Concurrency | Data Volume of a Single Table (table_size) | Total Number of Tables (tables) | TPS | QPS |
2 cores and 4 GB | 64 | 25000 | 250 | 1419.19 | 23733.31 |
4 cores and 8 GB | 128 | 25000 | 250 | 2582.92 | 43194.53 |
8 cores and 16 GB | 256 | 25000 | 250 | 4703.07 | 78650.06 |
8 cores and 32 GB | 512 | 25000 | 250 | 4767.48 | 79727.2 |
8 cores and 64 GB | 128 | 25000 | 250 | 4755.76 | 79531.15 |
16 cores and 64 GB | 128 | 25000 | 250 | 9041.06 | 151194.82 |
16 cores and 96 GB | 256 | 25000 | 250 | 9152 | 153050.09 |
16 cores and 128 GB | 128 | 25000 | 250 | 9231.56 | 154380.69 |
24 cores and 144 GB | 256 | 25000 | 250 | 13348.46 | 223228.12 |
32 cores and 128 GB | 256 | 25000 | 250 | 17708.45 | 296140.77 |
32 cores and 256 GB | 256 | 25000 | 250 | 18349.53 | 306861.71 |
64 cores and 256 GB | 256 | 25000 | 250 | 29011.12 | 485157 |
64 cores and 512 GB | 256 | 25000 | 250 | 29307.48 | 490113.07 |
88 cores and 710 GB | 256 | 25000 | 250 | 44376.07 | 742107.07 |
Scenario 4: Mixed Read-Write (point select)
Specifications | Concurrency | Data Volume of a Single Table (table_size) | Total Number of Tables (tables) | TPS | QPS |
2 cores and 4 GB | 64 | 25000 | 250 | 2482.47 | 33696.24 |
4 cores and 8 GB | 64 | 25000 | 250 | 4927.09 | 66878.78 |
8 cores and 16 GB | 128 | 25000 | 250 | 8954.96 | 121551.65 |
8 cores and 32 GB | 256 | 25000 | 250 | 9072.63 | 123148.86 |
8 cores and 64 GB | 256 | 25000 | 250 | 9206.17 | 124961.51 |
16 cores and 64 GB | 256 | 25000 | 250 | 17089.16 | 231962.71 |
16 cores and 96 GB | 256 | 25000 | 250 | 17211.07 | 233617.5 |
16 cores and 128 GB | 128 | 25000 | 250 | 17211.28 | 233620.29 |
24 cores and 144 GB | 256 | 25000 | 250 | 24042.79 | 326349 |
32 cores and 128 GB | 256 | 25000 | 250 | 30852.72 | 418784.82 |
32 cores and 256 GB | 256 | 25000 | 250 | 31218.51 | 423749.9 |
64 cores and 256 GB | 256 | 25000 | 250 | 40620.47 | 551369.09 |
64 cores and 512 GB | 256 | 25000 | 250 | 42912.72 | 582483.33 |
88 cores and 710 GB | 512 | 25000 | 250 | 59633.56 | 809446.57 |
Scenario 5: Write-Only
Specifications | Concurrency | Data Volume of a Single Table (table_size) | Total Number of Tables (tables) | TPS | QPS |
2 cores and 4 GB | 128 | 25000 | 250 | 4484.71 | 26232.98 |
4 cores and 8 GB | 128 | 25000 | 250 | 8721.67 | 51016.74 |
8 cores and 16 GB | 128 | 25000 | 250 | 17320.72 | 101316.26 |
8 cores and 32 GB | 128 | 25000 | 250 | 17462.34 | 102144.65 |
8 cores and 64 GB | 128 | 25000 | 250 | 17406.31 | 101816.95 |
16 cores and 64 GB | 128 | 25000 | 250 | 30520.5 | 178527.42 |
16 cores and 96 GB | 128 | 25000 | 250 | 31013.46 | 181410.96 |
16 cores and 128 GB | 128 | 25000 | 250 | 30817.17 | 180262.74 |
24 cores and 144 GB | 1024 | 25000 | 250 | 40442.94 | 236567.99 |
32 cores and 128 GB | 1024 | 25000 | 250 | 49978.26 | 292344.16 |
32 cores and 256 GB | 1024 | 25000 | 250 | 52943.68 | 309690.15 |
64 cores and 256 GB | 1024 | 25000 | 250 | 67546.8 | 395110.02 |
64 cores and 512 GB | 1024 | 25000 | 250 | 67512.79 | 394911.08 |
88 cores and 710 GB | 1500 | 25000 | 250 | 86731.1 | 507327.18 |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback