Selection Guide
Baixar
Modo Foco
Tamanho da Fonte
Before purchasing a TencentDB for MySQL instance, you need to understand the characteristics of different instances to select the appropriate one based on your business requirements.
Instance Selection Guide
Before purchasing a TencentDB for MySQL instance, you need to consider factors such as price, performance, workload, and business use cases to ensure you can purchase a suitable instance with the best cost-effectiveness. The database storage engine, instance architecture, storage type, and isolation policy are closely related and mutually influential, which may cause confusion when you select. Therefore, this document briefly introduces these aspects to help you select the appropriate instance.
I. Database Storage Engines
A storage engine refers to the type of a table. The database storage engine determines how tables are stored on a computer.
InnoDB: The most commonly used OLTP storage engine. It employs Multi-Version Concurrency Control (MVCC) and row-level locking technologies to deliver high-performance and reliable transaction processing capabilities. Compared to other MySQL storage engines, InnoDB offers superior data integrity, including features such as foreign keys and rollback, and provides more advanced query functionality. Tencent Cloud has also implemented numerous kernel optimizations for InnoDB, giving it a more significant performance advantage. Consequently, it is widely used in high-performance, high-concurrency use cases.
RocksDB: A highly popular high-performance persistent KV (key-value) store. TXRocks is a transactional storage engine developed by Tencent's TXSQL team based on this engine. By leveraging the LSM Tree storage structure of RocksDB, TXRocks minimizes wastage caused by partially filled InnoDB pages and fragmentation, while also supporting a compact data format. Consequently, TXRocks can achieve storage efficiency, using only half or even less space compared to InnoDB, without compromising on performance. It is particularly well-suited for applications that demand high transaction read/write performance and manage large volumes of data.
LibraDB: A self-developed OLAP storage engine. With capabilities such as columnar storage, large-scale concurrency execution, and the vectorized execution engine, LibraDB accelerates various complex and time-consuming SQL queries such as complex queries, slow SQL queries, and fuzzy matching in the business, effectively improving the overall SQL execution efficiency. LibraDB is suitable for use cases such as real-time reporting, online analysis, and HTAP. Currently, only read-only instances support the LibraDB engine.
II. Instance Architecture
TencentDB for MySQL supports four instance architectures: single-node, two-node, three-node, and Cluster Edition.
Architecture | Description | Scenarios |
Single-Node | Supported versions: MySQL 5.7 and 8.0 Node: a single node. | Personal learning, micro-websites, non-core small systems for enterprises, and development and testing environments for medium and large enterprises. |
Two-Node | Supported versions: MySQL 5.6, 5.7, and 8.0. Node: one primary node and one secondary node. Primary-secondary replication mode: asynchronous and semi-synchronous (default) | Gaming, Internet, IoT, retail e-commerce, logistics, insurance, and security industry applications. |
Three-Node | Supported versions: MySQL 5.6, 5.7, and 8.0. Node: one primary node and two secondary nodes. Primary-secondary replication modes: asynchronous, strongly synchronous, or semi-synchronous (default). | Gaming, Internet, IoT, retail e-commerce, logistics, insurance, and security industry applications. |
Cluster Edition | Supported versions: MySQL 5.7 and 8.0 Node: one read-write node and up to 5 read-only nodes Primary-secondary replication mode: asynchronous and semi-synchronous (default) | Gaming, Internet, IoT, retail e-commerce, logistics, insurance, and security industry applications. |
III. Storage Types
TencentDB for MySQL supports local SSD disks, Cloud SSD, Premium Disk, Enhanced SSD, and Extreme SSD for its underlying storage.
Performance Metric | Tremendoust SSD Cloud Disk | Enhanced SSD Cloud Disk | Premium Disk | SSD | Local SSD |
Maximum capacity of a single disk (GB) | 32000 | 32000 | 32000 | 32000 | 12000GB |
Maximum IOPS of a single disk | Up to 1,000,000 after adding additional performance | Up to 100,000 after additional performance is added | 6000 | 26000 | 150000 |
Calculation formula for random IOPS performance. | Benchmark performance
: Random IOPS = min{4000 + Capacity (GiB) x 100, 50000}
Additional performance
: Maximum IOPS =
min{Additional performance value x 128, 950000} | Benchmark performance: Random IOPS = min{1800 + Capacity (GiB) x 50, 50000} Additional performance: Maximum IOPS = min{Additional performance value x 128, 50000}. For details, see Enhanced Cloud SSD Performance Specifications. | Random IOPS = min{1800 + Capacity (GiB) x 8, 6000} | Random IOPS = min{1800 + Capacity (GiB) x 30, 26000} | |
Maximum throughput of a single disk (MB/s) | Up to 4,000 MB/s after adding additional performance | Up to 1,000 MB/s after additional performance is added | 150MB/s | 260MB/s | - |
Throughput performance calculation formula (MB/s) | Benchmark performance: Throughput = min{120 + Capacity (GiB) x 0.5, 350}
Additional performance: Throughput = min{Additional performance value x 1, 3650} | Benchmark performance: Throughput = min{120 + Capacity (GiB) x 0.5, 350} Additional performance: Throughput = min{Additional performance value x 1, 650}. For details, see Enhanced Cloud SSD Performance Specifications. | Throughput = min{100 + Capacity (GiB) x 0.15, 150} | Throughput = min{120 + Capacity (GiB) x 0.2, 260} | - |
Single-path random read/write latency (ms) | 0.1ms - 0.5ms | 0.2ms - 1ms | 0.8ms - 5ms | 0.5ms - 3ms | Microsecond-level |
IV. Isolation Policy
The isolation policies of TencentDB for MySQL include basic, economical, general, exclusive, standard, enhanced, and flagship types.
Isolation Policy | Description |
Basic | Only single-node supports the basic isolation policy (formerly Basic Edition), with storage-computing separation and cloud disk storage at the underlying layer. |
Economical | Exclusive memory and disk allocation for instances. CPU resources are shared among general specification instances located on the same physical server.* Fixed instance specifications and disk capacity. Suitable for lightweight and low-load use cases such as small websites, Web applications, blogs, forums, and cloud development/test/learning environments, offering excellent cost performance. |
General | Exclusive memory and disk allocation for instances. CPU resources are shared among general specification instances located on the same physical server.* It offers excellent cost performance by leveraging economies of scale through resource sharing, with CPU resources being lightly shared. |
Exclusive | The instance has exclusive access to CPU (with core binding), memory, and disk resources, ensuring long-term stable performance that is not affected by the behavior of other instances on the same physical machine. The highest tier of the dedicated specification is a dedicated physical server, which exclusively utilizes all resources of a single physical machine. |
Standard | Exclusive CPU and memory allocation for instances, with long-term stable performance. Storage-computing separation architecture with flexible configurations. |
Enhanced | Exclusive CPU and memory allocation for instances, with long-term stable performance. Storage-computing separation architecture with flexible configurations. Tremendous SSD is supported, providing stable and reliable performance. |
Flagship | CPU core with a higher frequency, offering outstanding performance. Exclusive CPU and memory allocation for instances, with long-term stable performance. Storage-computing separation architecture with flexible configurations. Tremendous SSD is supported, providing stable and reliable performance. |
*In extreme cases, resource contention may occur (extremely low probability) for the general isolation policies.
Getting Started with Selection
You can refer to the following steps for instance selection:
1. Select a Database Storage Engine.
If you need full transaction support and strong read-write concurrency, InnoDB is recommended. To reduce storage costs, RocksDB is recommended, which can save up to half or more of the storage space compared to InnoDB while offering similar performance. For use cases such as real-time reporting, online analysis, and HTAP, it is recommended to add the LibraDB read-only analysis engine after you create two-node or three-node architecture instances, effectively improving the overall SQL execution efficiency.
2. Select an Instance Architecture.
Typically, you can choose the two-node architecture, which adopts the classic high-availability setup of one primary and one standby node. This architecture is suitable for industries such as the internet, IoT, retail e-commerce, logistics, and gaming, as well as for medium and large enterprises.
If you require financial-grade reliability, high security, high availability, and high disaster recovery capabilities, and your business is similar to those in the finance, securities, or insurance industries, or involves core databases of large enterprises, the three-node architecture is recommended.
If your business is complex, involves frequent changes, handles large data volumes, requires high read performance, and needs frequent scaling or addition/deletion of read-only instances, while also requiring high reliability, security, availability, and disaster recovery capabilities, Cluster Edition is recommended.
If you use it for personal learning, micro-websites, non-core small systems for enterprises, or development and testing environments for medium and large enterprises, the single-node architecture is recommended.
3. Select a Storage Type.
In terms of storage types, the instances with two-node or three-node architecture currently support local SSD; the single-node architecture instances support Cloud SSD, Premium Disk, and Enhanced SSD; the Cluster Edition architecture instances support Tremendous SSD, Enhanced SSD, Premium Disk, and Cloud SSD.
The single-node cloud disk architecture instance is implemented based on a cloud-native architecture. It is suitable for scenarios such as testing, development, and personal learning, supports up to 30 TB of storage space, and the storage capacity size affects IOPS.
4. Select an Isolation Policy and Instance Specifications
The single-node architecture supports the basic isolation policy. The two-node architecture supports the economical, general, and dedicated isolation policies. The three-node architecture supports the general and dedicated isolation policies. The cloud disk edition architecture supports the standard, enhanced, and flagship isolation policies. Instance specifications include parameters such as vCPU, memory, maximum IOPS, and maximum storage capacity. You can select the appropriate ones based on your business needs.
Note:
References
Ajuda e Suporte
Esta página foi útil?
Você também pode entrar em contato com a Equipe de vendas ou Enviar um tíquete em caso de ajuda.
comentários