Databases with excellent performance and scalability can help you quickly increase the load capacity of your existing systems. With the same size of database, TencentDB for MySQL, if appropriately used, can significantly improve database concurrence for higher QPS.
TencentDB for MySQL is currently available in v5.5, v5.6, v5.7, and v8.0, all of which are fully compatible with native MySQL. You are recommended to choose v5.6 and higher, as they use more stable database kernels, deliver better system performance by optimizing the design of v5.5 and lower, and come with a lot of appealing new features.
This document takes MySQL v5.7 as an example to illustrate the features of the new versions. This version is widely recognized for its impressive performance, reliability, and ease of use. Some of its improvements and new features are as shown below:
With MySQL v5.7, you can seamlessly integrate the best relational samples with the best document samples in one tool so as to use the most appropriate ones out of them in different applications and use cases, which greatly expands your range of applications.
SELECT feature->"$.properties.STREET" AS property_street FROM features WHERE id = 121254;
For more information on improvements and new features in MySQL v5.7, see MySQL's official documentation.
Currently, TencentDB for MySQL doesn't offer separate CPU options; instead, the CPU will be allocated proportionally according to the memory specification. You can purchase database specifications based on your business characteristics. We have conducted thorough benchmark tests on each type of instance so as to provide performance information for your reference when you select specifications.
However, it should be noted that the sysbench-enabled tests cannot represent all business scenarios. You are recommended to perform stress testing on your instance before launching it officially, so that you can better understand how TencentDB for MySQL performs in your business scenario. For more information, see MySQL Performance Description.
Memory is one of the core instance metrics, which features an access speed much higher than that of a disk. Generally, the more data cached in the memory, the faster the database response. If the memory is small, after the stored data exceeds a certain amount, the excessive data will be stored to the disk. After that, when a new request accesses the data again, the data will be read from the disk into the memory, consuming disk IO and leading to slower database response.
For businesses with high read concurrence or sensitive to read delay, it is recommended to choose a higher memory specification so as to ensure high database performance.
The disk capacity of a TencentDB for MySQL instance includes only the MySQL data directories but not the logs such as binlog, relaylog, undolog, errorlog, and slowlog. When the amount of written data exceeds the instance disk capacity, if the instance is not upgraded, instance lock may be triggered. Therefore, when you purchase a disk, you are recommended to take into account the possible data volume increase in the future and select a larger disk, which helps prevent your instance from being locked or frequently upgraded due to insufficient disk capacity.
TencentDB for MySQL provides three replication modes: async, semi-sync, and strong sync. For more information, see Database Instance Replication Mode. If your business is sensitive to write latency or database performance, you are recommended to choose the async replication mode.
High availability of TencentDB for MySQL is guaranteed by the master/slave and master/master architecture. Master-slave data sync is achieved through binlogs. In addition, the database can be rolled back to any previous point in time, which relies on backups and logs. Therefore, you generally do not need to set up a backup and restoration system on your own or pay additional fees to keep your instance highly available.
All the different database versions and memory/disk specifications of TencentDB for MySQL support online dynamic hot upgrade. The upgrade process will not interrupt your business, eliminating your concerns over any database bottlenecks caused by business growth.
After a purchase is made, you generally need to use CVM and TencentDB for MySQL together. For more information, see Accessing TencentDB for MySQL from CVM.
In common internet-based businesses, the read/write ratio of databases generally ranges from 4:1 to 10:1, which means that the read load of databases is much higher than the write load. When a performance bottleneck occurs, a common solution is to increase the read load.
TencentDB for MySQL read-only instances are ideal for such issues. For more information, see Read-only Instance.
Read-only instances can also be used for read-only access in various businesses; for example, the master instance undertakes read/write access for online businesses, while the read-only instance provides read-only query for internal businesses or data analysis platforms.
TencentDB for MySQL provides disaster recovery instances, helping you quickly set up remote disaster recovery for databases.
With the help of disaster recovery instances, multiple data centers in different regions can act as redundancy of each other, so that when one data center cannot provide a service due to failures or force majeure events, the service can be quickly switched to another data center. Disaster recovery instances use private network Direct Connect lines of Tencent Cloud to implement data sync, which can minimize the impact of delayed sync on your business when a disaster occurs. As long as the remote service logic is ready, the disaster recovery switchover can be completed in seconds.
With TencentDB for MySQL, it only takes several simple steps to configure the 2-region-3-DC scheme:
A disaster recovery instance also adopts the high-availability master/slave and master/master architecture. In addition, it can be accessed in a read-only manner, which helps enable local access to your businesses for end users in different regions.