tencent cloud

Feedback

Test Results - Big Dataset Scenario

Last updated: 2022-04-13 12:04:11

    This document lists the performance comparison test results between TDSQL-C for MySQL and TencentDB for MySQL in the big dataset scenario.

    Big Dataset Scenario Overview

    In the big dataset scenario, the entire volume of data cannot be all stored in the cache (the data volume is twice the memory size), and the disk needs to be read and written to update the cache during queries.

    Big Dataset Scenario Test Conclusion

    • In the read scenario, TDSQL-C for MySQL can achieve a CPU utilization of above 90% on compute nodes. The test shows that the resource utilization of TDSQL-C for MySQL is better than that of TencentDB for MySQL.
    • In the write scenario, TDSQL-C for MySQL outperforms TencentDB for MySQL under lower specifications, and as the specifications and data volume increase, its performance advantage gets much greater.
    Dataset CharacteristicsTest ScenarioRead TypeConclusion
    Big datasetWrite-TDSQL-C for MySQL outperforms TencentDB for MySQL, especially under high specifications
    ReadPOINT SELECTTDSQL-C for MySQL has a higher performance
    ReadRANGE SELECTTDSQL-C for MySQL and TencentDB for MySQL have generally the same performance under most specifications
    Read-writePOINT SELECTTDSQL-C for MySQL has a higher performance
    Read-writeRANGE SELECTTDSQL-C for MySQL and TencentDB for MySQL have generally the same performance under most specifications

    Big Dataset Scenario Test Results

    Scenario 1: Write

    Specification Concurrency Table Size Tables QPS
    TencentDB for MySQL TDSQL-C for MySQL
    2-core 16 GB MEM968000001501477226864
    4-core 16 GB MEM968000003003114045881
    4-core 32 GB MEM1928000003003153953082
    8-core 32 GB MEM1928000003005439797005
    8-core 64 GB MEM1928000004505494592988
    16-core 64 GB MEM19280000045060948111596
    16-core 96 GB MEM25680000060079163109014
    16-core 128 GB MEM3845000000300105781142165
    32-core 128 GB MEM384500000030081662252668
    32-core 256 GB MEM3845000000400101277270367
    64-core 256 GB MEM3846000000450115992301974

    Scenario 2: Read (POINT SELECT)

    Specification Concurrency Table Size Tables QPS
    TencentDB for MySQL TDSQL-C for MySQL
    2-core 16 GB MEM5128000001503859445597
    4-core 16 GB MEM5128000003007311775483
    4-core 32 GB MEM10008000003007466492117
    8-core 32 GB MEM1000800000300142866181402
    8-core 64 GB MEM1000800000450149526172378
    16-core 64 GB MEM1000800000450303341325878
    16-core 96 GB MEM1000800000600311256336011
    16-core 128 GB MEM10005000000300262724323877
    32-core 128 GB MEM10005000000300483449573631
    32-core 256 GB MEM10005000000400474329615283
    64-core 256 GB MEM10006000000450663715940105

    Scenario 3: Read (RANGE SELECT)

    Specification Concurrency Table Size Tables QPS
    TencentDB for MySQL TDSQL-C for MySQL
    2-core 16 GB MEM648000001501357114388
    4-core 16 GB MEM648000003002896226079
    4-core 32 GB MEM648000003003004528314
    8-core 32 GB MEM648000003004729857353
    8-core 64 GB MEM648000004505863857281
    16-core 64 GB MEM12880000045010407298246
    16-core 96 GB MEM128800000600114502106160
    16-core 128 GB MEM1285000000300121297109978
    32-core 128 GB MEM2565000000300192649183658
    32-core 256 GB MEM2565000000400185941184855
    64-core 256 GB MEM2566000000450283903278997

    Scenario 4: Read-write (POINT SELECT)

    Specification Concurrency Table Size Tables QPS
    TencentDB for MySQL TDSQL-C for MySQL
    2-core 16 GB MEM648000001502072622997
    4-core 16 GB MEM2568000003004782051545
    4-core 32 GB MEM2568000003005268062105
    8-core 32 GB MEM25680000030094132108540
    8-core 64 GB MEM256800000450100882120153
    16-core 64 GB MEM256800000450192474193744
    16-core 96 GB MEM256800000600186854184257
    16-core 128 GB MEM5125000000300188389195375
    32-core 128 GB MEM5125000000300227494306809
    32-core 256 GB MEM5125000000400245819307072
    64-core 256 GB MEM5126000000450335819453163

    Scenario 5: Read-write (RANGE SELECT)

    Specification Concurrency Table Size Tables QPS
    TencentDB for MySQL TDSQL-C for MySQL
    2-core 16 GB MEM328000001501317713883
    4-core 16 GB MEM328000003002793520720
    4-core 32 GB MEM648000003003070529914
    8-core 32 GB MEM968000003005016658060
    8-core 64 GB MEM648000004505786653804
    16-core 64 GB MEM12880000045010792395976
    16-core 96 GB MEM128800000600107589107180
    16-core 128 GB MEM2565000000300138710110169
    32-core 128 GB MEM2565000000300165299180335
    32-core 256 GB MEM2565000000400166066171670
    64-core 256 GB MEM5126000000450208616190824
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support