This document describes three resource isolation policies of TencentDB for MySQL: basic, general, and dedicated.
Note:
- The former "Basic Edition" has been renamed "basic single-node", and the former "Single-Node High IO Edition" has been renamed "general single-node".
- Two-node and three-node architectures support general and dedicated isolation policies.
Resource Isolation Policy | Description |
---|---|
Basic | Single-node instances are the only ones that support this policy. A basic single-node instance (formerly Basic Edition) supports computation-storage separation and stores data on cloud disks. |
General | |
Dedicated |
TencentDB for MySQL single-node (cloud disk) instances are deployed based on TKE, where each instance has dedicated CPU, memory, and disk resources and different instances are completely isolated from each other.
TencentDB for MySQL two-node (local disk) and three-node (local disk) instances are deployed based on local physical machines. Each physical machine sustains multiple instances and adopts isolation policies to ensure the complete isolation between different instances with dedicated CPU, memory, and disk resources.
In addition, TencentDB for MySQL also implements corresponding data isolation policies in multiple dimensions such as account, region, AZ, and network.
Was this page helpful?