tencent cloud

Feedback

MySQL 5.7 Test Results

Last updated: 2022-03-24 15:12:45

    This document describes the performance test results of a general TencentDB for MySQL 5.7 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 649.18 12983.6 12.32
    1 2000 8 25000 150 695.27 13905.4 11.51
    2 4000 16 25000 150 1409.01 28180.1 11.35
    4 8000 32 25000 150 2518.13 50362.6 12.71
    4 16000 32 25000 150 2424.66 48493.2 13.2
    8 16000 64 25000 150 4235.31 84706.2 15.11
    8 32000 64 25000 150 4112.97 82259.5 15.56
    16 32000 128 25000 150 7154.77 143095 17.88
    16 64000 128 25000 150 7888.35 157767 16.22
    16 96000 128 25000 150 7902.25 158045 16.19
    16 128000 128 25000 150 7910.24 158205 16.17

    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.

    CPU
    (Core)
    Memory
    (MB)
    Concurrency Data Volume/Table Total Tables SysBench TPS SysBench QPS avg_lat
    1 1000 8 800000 6 625.6 12512 12.79
    1 2000 8 800000 12 691.34 13826.7 11.57
    2 4000 16 800000 24 1353.43 27068.7 11.82
    4 8000 32 800000 48 2491.65 49832.9 12.84
    4 16000 32 6000000 13 2343.67 46873.4 13.65
    8 16000 64 6000000 13 4075.31 81506.2 15.7
    8 32000 64 6000000 25 3895.22 77904.3 16.43
    16 32000 128 6000000 25 6612.82 132256 19.35
    16 64000 128 6000000 49 6995.9 139918 18.29
    16 96000 128 6000000 74 6985.35 139707 18.32
    16 128000 128 6000000 98 6980.42 139608 18.33
    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