All Products
Search

This Product

    :Test results of ApsaraDB RDS instances that run MySQL 5.6

    Document Center

    :Test results of ApsaraDB RDS instances that run MySQL 5.6

    Last Updated:Oct 25, 2023

    This topic describes the performance test results of general-purpose ApsaraDB RDS instances that run MySQL 5.6.

    Note

    Environment

    In this stress testing, SysBench is used to test the performance of the five RDS instances that use local disks. These RDS instances use different instance types.

    • Instance types: rds.mysql.t1.small, rds.mysql.s2.large, rds.mysql.m1.medium, rds.mysql.c1.xlarge, and rds.mysql.c2.xlarge

    • Instance family: general-purpose

    • Edition: RDS High-availability Edition

    • Storage type: local disk

    Configurations

    The performance is significantly affected by the data volume, stress testing duration, and parameter settings. The following configurations are used for this stress testing:

    • Data volume: The data volume and the number of tables on each RDS instance that you want to test are different. Therefore, the test results for some of the five RDS instances may be similar.

    • Stress testing duration: The stress testing duration is 60 seconds for all the RDS instances.

    • Parameter settings:

      • sync_binlog=1and innodb_flush_log_at_trx_commit=1: ensure that the data submitted each time is completely written to disks.

      • rpl_semi_sync_master_enabled=ON: enables the semi-synchronous mode for an RDS instance to ensure data consistency between the primary and secondary RDS instances.

      • Performance_schema=ON: automatically enables Performance Schema for RDS instances that use instance types with a memory size greater than or equal to 8 GB.

        Note

        These parameter settings are contained in the standard parameter template for ApsaraDB RDS for MySQL. If the standard parameter template is applied to all the RDS instances, data consistency is maximized, and the test environment is more similar to the production environment.

    Results

    Two types of queries can be used to perform stress testing. You can determine the type of stress testing based on your data volume.

    • Stress testing for cache-based queries: This type of stress testing is suitable for scenarios that involve a small amount of data. You can store all data in the InnoDB buffer pool for access. For more information about how to change the size of the InnoDB buffer pool, see Change the size of the InnoDB buffer pool for an ApsaraDB RDS for MySQL instance.

    • Stress testing for disk I/O-based queries: This type of stress testing is suitable for scenarios that involve a large amount of data. You can store only the most frequently used data in the InnoDB buffer pool for access. During the stress testing, data is read from or written to disks, and the InnoDB buffer pool is updated.

    Type 1: Stress testing for cache-based queries

    内存命中型

    Specification (instance type)

    Data volume in a single table

    Number of tables

    Maximum number of connections

    IOPS

    Number of SysBench threads

    Number of SysBench reads

    Number of SysBench writes

    1 core and 1 GB of memory

    (rds.mysql.t1.small)

    25000

    32

    300

    600

    8

    450394

    128684

    2 cores and 4 GB of memory

    (rds.mysql.s2.large)

    25000

    32

    1200

    2000

    8

    1045100

    298598

    4 cores and 16 GB of memory

    (rds.mysql.m1.medium)

    25000

    128

    4000

    7000

    16

    1063846

    303956

    8 cores and 32 GB of memory

    (rds.mysql.c1.xlarge)

    25000

    128

    8000

    12000

    32

    2177504

    622144

    16 cores and 64 GB of memory

    (rds.mysql.c2.xlarge)

    25000

    128

    16000

    14000

    64

    4686654

    1339044

    Type 2: Stress testing for disk I/O-based queries

    磁盘I/O型

    Specification (instance type)

    Data volume in a single table

    Number of tables

    Maximum number of connections

    IOPS

    Number of SysBench threads

    Number of SysBench reads

    Number of SysBench writes

    1 core and 1 GB of memory

    (rds.mysql.t1.small)

    80000

    32

    300

    600

    8

    406238

    116068

    2 cores and 4 GB of memory

    (rds.mysql.s2.large)

    80000

    32

    1200

    2000

    8

    1013614

    289604

    4 cores and 16 GB of memory

    (rds.mysql.m1.medium)

    800000

    128

    4000

    7000

    16

    1040154

    295768

    8 cores and 32 GB of memory

    (rds.mysql.c1.xlarge)

    800000

    128

    8000

    12000

    32

    2119922

    605692

    16 cores and 64 GB of memory

    (rds.mysql.c2.xlarge)

    800000

    128

    16000

    14000

    64

    4434220

    1266920