TencentDB for MySQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Database Architecture
- Database Instance
- Kernel Features
- Kernel Version Release Notes
- Functionality Features
- Performance Features
- Parallel Query
- Security Features
- Stability Features
- Purchase Guide
- Getting Started
- Connecting to MySQL Instance
- Database Audit
- Audit Rule Template
- MySQL Cluster Edition
- Maintenance Management Instance
- Operation Guide
- Instance Management and Maintenance
- Instance Upgrade
- CPU Elastic Expansion
- Read-Only/Disaster Recovery Instances
- Database Proxy
- Database Proxy Kernel Features
- Database Proxy Management
- Automatic Read/Write Separation Feature
- Connection Pool Feature
- Other Features
- Account Management
- Database Management Center (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Restoring Database from Backup File
- Monitoring and Alarms
- Operation Logs
- Practical Tutorial
- Calling MySQL APIs in Python
- White Paper
- Performance White Paper
- Performance Test Report
- Troubleshooting
- Connections
- API Documentation
- Data Import APIs
- Rollback APIs
- Parameter APIs
- Making API Requests
- Instance APIs
- Database Proxy APIs
- Database Audit APIs
- Security APIs
- Account APIs
- Backup APIs
- Database APIs
- Monitoring APIs
- Log-related API
- FAQs
- Backup
- Connection and Login
- Instance Upgrade
- Performance and Memory
- Service Agreement
- Reference
Resource Isolation Policy
Last updated: 2024-11-06 19:15:37
This document describes the isolation policies of TencentDB for MySQL, including basic , general, dedicated, standard, and enhanced types.
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.
The Cluster Edition architecture supports both standard and enhanced isolation policies.
Architecture | Resource Isolation Policy | Description |
Single-node (cloud disk) | 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. |
Two-node (local disk) Three-node (local disk) | General | A general instance exclusively uses the allocated memory and disk resources and shares the CPU resources with other general instances on the same physical machine. * A general instance benefits from higher specifications at a lower cost by sharing CPU resources. |
Two-node (local disk) Three-node (local disk) | Dedicated | A dedicated instance has exclusive access to the CPU, memory, and disk resources (if CPU pinning is enabled). It has long-term stability and is unaffected by the activities of other instances on the physical machine. A dedicated instance with the highest configurations can monopolize a physical machine and all of its resources. |
Cluster Edition (cloud disk) | Standard Type | Exclusive allocation of CPU and memory ensures long-term stable performance. A decoupled architecture of computing and storage offers flexible configuration options. |
Cluster Edition (cloud disk) | Enhanced Type | Enhanced frequency CPU cores deliver optimal performance. Exclusive allocation of CPU and memory ensures long-term stable performance. A decoupled architecture of computing and storage offers flexible configuration options. Supports Tremendous SSD cloud disk, providing stable and reliable performance. |
*There may be resource contention for the general type in extreme cases (very low probability).
Isolation policies for different architectures
For TencentDB for MySQL, both the single node (cloud disk edition) and the Cluster Edition (cloud disk edition), are deployed on the cloud-native TKE, with each instance enjoying dedicated CPU, memory, and disk resources, ensuring complete isolation between different instances.
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?
You can also Contact Sales or Submit a Ticket for help.
Yes
No