tencent cloud

PrevNext

Feedback

search by keyword

Recent Pages

Documentation
TencentDB for MySQL
    Documentation
    Download PDF

    Related to Selection

    Last updated: 2023-12-27 11:05:48
    Download PDF

      How do I select an appropriate TencentDB for MySQL instance?

      Before purchasing a MySQL instance, it is crucial to understand the features of different instances. This can help you select one that best suits your operations. This section provides guidance on how to select a MySQL instance that is suitable for your business needs.

      Instance Information

      Before purchasing a MySQL instance, it is essential to consider factors such as price, performance, workload, and business usage scenarios so that you can buy an instance with high cost-effectiveness. As elements such as database storage engine, instance architecture, storage type, and resource isolation policy are closely intertwined and can impact one another, you might feel confused during the selection process. Therefore, this section provides a concise overview of these aspects to help you in selecting a suitable instance.

      1. Database Storage Engine

      A storage engine refers to the type of tables. The storage engine of database determines the manner in which tables are stored in a computer.
      InnoDB: The most frequently used OLTP storage engine, uses multi-version concurrency control (MVCC) and row-level locking technologies, offering high performance and reliable processing capabilities. In comparison to other MySQL storage engines, InnoDB offers functions including data foreign key and rollback, ensuring better data integrity. It also provides higher-level query functionalities. InnoDB kernel has been optimized a lot by Tencent Cloud and therefore has great performance advantages and is extensively applied in scenarios that involve high concurrency and require high performance.
      RocksDB: A widely popular high-performance persistent key-value (KV) store, TXRocks is a transactional storage engine developed by Tencent's TXSQL team based on RocksDB. Thanks to the RocksDB LSM Tree storage structure, TXRocks reduces the waste caused by the half-full page and fragmentation mechanism of InnoDB, while also supporting the compact storage formats. Therefore, while providing similar performance as InnoDB, TXRocks can save up to half or even more storage space compared to InnoDB. This makes it more suitable for business scenarios that require high read-write performance and involve large data volumes.

      2. Instance Architecture

      CDB MySQL supports three types of instance architectures: single-node, two-node, and three-node.
      
      Architecture
      Description
      Applicable Scenarios
      Single-Node
      Supported versions: MySQL 5.7 and 8.0.
      Node: Single Node.
      Personal learning, micro-websites, non-core small-scale enterprise systems, and the development and testing environments of large and medium-sized corporations.
      Two-Node
      Supported versions: MySQL 5.6, 5.7, and 8.0.
      Nodes: One Primary and One Standby.
      Primary-Standby Replication Mode: Asynchronous (default) and Semi-Synchronous
      Gaming, internet, IoT, retailing e-commerce, logistics, insurance, and securities, etc.
      Three-Node
      Supported versions: MySQL 5.6, 5.7, and 8.0.
      Nodes: One Primary and Two Standbys.
      Primary-Standby Replication Mode: Asynchronous (default), Strong-synchronous, and Semi-Synchronous
      Gaming, internet, IoT, retailing e-commerce, logistics, insurance, and securities, etc.

      III. Storage Classification

      The underlying storage of TencentDB for MySQL accommodates Local SSD, SSD CBS and Enhanced SSD CBS.
      Performance Metrics
      Enhanced SSD CBS
      SSD CBS
      Local SSD
      Maximum Capacity per Disk (GB)
      30000
      30000
      12000
      Maximum IOPS per Disk
      Reaches 100,000 with additional performance included
      26000
      150000
      Calculation Formula of Random IOPS
      Baseline Performance: Random IOPS = min{1800 + Capacity (GiB) 50, 50000} Extra Performance: Maximum IOPS = min{Extra Performance Value 128, 50000} For more details, please refer to Enhanced SSD CBS Performance Description
      Random IOPS = min{1800 + Capacity (GiB) * 30, 26,000}
      IOPS is relevant to the instance specifications. For details, see Instance Specification.
      Maximum Throughput per Disk (MB/s)
      Reaches 1,000 with additional performance
      260
      -
      Throughput Calculation Formula (MB/s)
      Baseline Performance: Throughput = min{120 + Capacity (GiB) 0.5, 350} Additional Performance: Throughput = min{Additional Performance Value 1, 650} For details, please refer to Enhanced SSD CBS Performance Description.
      Throughput = min{120 + Capacity (GiB) * 0.2, 260}
      -
      One-Way Random Read/Write Latency (ms)
      0.2 - 1
      0.5 - 3
      Microsecond-level

      IV. Resource Isolation Policy

      The resource isolation policies of CDB, including basic, general, and dedicated.
      Resource Isolation Policy
      Description
      Basic Type
      Only single-node instances support the basic isolation policy (formerly basic edition), where there is a separation between computing and storage, with the underlying layer using cloud disk storage.
      General Type
      An instance exclusively utilizes allocated memory and disk resources while sharing CPU resources with other general instances on the same physical machine.
      Benefit from resource sharing, bringing higher cost-effectiveness and minor CPU resource reutilization.
      The disk capacity is not tied to the CPU and memory, allowing for flexible matching.
      Dedicated Type
      An instance has dedicated CPU (with core binding), memory, and disk resources. It promises long-term performance stability and remains unaffected by the behavior of other instances on the physical machine.
      The peak configuration of the dedicated type is to occupy a physical machine alone, taking full control over all its resources.

      Product Selection

      You can follow the following steps to select an instance:
      1. Selecting Database Storage Engine
      If you require full transaction support and robust read-write concurrency capabilities, InnoDB is recommended.
      If you want to reduce storage costs, RocksDB is recommended. It uses about half or even less storage space compared to InnoDB, while still providing similar performance.
      2. Selecting Instance Architecture
      Single-Node: Applies to scenarios such as personal learning, sparse websites, non-core small business systems, and the development and testing environments for medium to large-sized enterprises.
      Two-Node: Adopts the classic master-slave high-availability architecture, ideal for internet, IoT, retailing e-commerce, logistics, gaming industries, or medium to large-sized enterprises.
      Three-Node: Necessary for finance-grade reliability, high security, high availability, high disaster recovery capabilities, resembling business of financial, securities, insurance industries, or core database of large enterprises.
      3. Selecting Storage Type
      For both two-node and three-node architecture instances, the currently supported storage type is local SSD disk. For single-node architecture instances, the supported storage types are SSD CBS and enhanced SSD CBS.
      Instances with single-node cloud disk architecture are based on cloud-native design, fulfilling requirements in scenarios such as testing, development, and personal learning. They offer a maximum of 30 TB storage space. The size of storage space has an impact on IOPS.
      For the performance metrics of different storage types, see Storage Types.
      4. Selecting Resource Isolation Policy and Instance Specifications
      A single-node architecture supports a basic isolation policy, whereas both two-node and three-node architectures support general and dedicated isolation policies. The instance specifications include parameters such as vCPU, memory, max IOPS, and max storage capacity. You can select the most suitable resource isolation policy and instance specifications based on your business requirements.
      Note：
      For details about all available models and selection options, please see Purchase Methods.

      Related Documents

      Architecture Overview
      Resource Isolation Policy
      Database Instance Type
      Database Instance Replication
      Database Instance Specifications
      
      Contact Us

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

      Contact Us
      Technical Support

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

      Submit a Ticket
      7x24 Phone Support
      Copyright © 2013-2024 Tencent Cloud. All Rights Reserved.
      Privacy PolicyLegalCookie Policy