MySQL sync versions and configurations
Versions
MySQL sync version 8 is supported.
Node configurations
When creating a MySQL sync Managed Database cluster, you can select the node configuration—the number of vCPUs, RAM, and disk size.
Available node configurations are divided into lines. Depending on the line, configuration, and location, different processors and volumes are used.
When choosing a configuration, keep in mind that a portion of the disk space is reserved for system tasks and is not available for database storage. Learn more in the guide Using disk space in the MySQL sync cluster.
After creating a cluster, you can change the node configuration— scale the cluster.
Configuration lines
The resource ratio in configuration lines can be:
To see the availability of configuration lines in regions, see the Managed Databases availability matrix.
Standard
A line of fixed configurations with a local disk and a balanced vCPU:RAM ratio, suitable for most DBMS. We recommend using this line if you do not know your workload profile.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. You can view the processor frequency in different lines in the Processors table.
To view disk performance and bandwidth in different lines, see the Performance and Bandwidth table.
CPU
A line of fixed configurations with a local disk and a balanced vCPU:RAM ratio. Suitable for workload profiles that are computationally demanding. For example, if the database runs analytic queries, multiple nested queries, or data encryption. One way to determine such a workload profile is to monitor the Load Average metric, which shows the average system load over one, five, or 15 minutes.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. You can view the processor frequency in different lines in the Processors table.
To view disk performance and bandwidth in different lines, see the Performance and Bandwidth table.
Memory
A line of fixed configurations with local disk and a balanced vCPU:RAM ratio. Suitable for workload profiles that are demanding of caching. For example, if multiple, infrequently repeated queries to different parts of tables are performed in the database. One way to determine such a workload profile is to monitor the Cache_hit_ratio (Cache_hit_ratio) metric, which shows the percentage of data in a query that is read from the cache.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. You can view the processor frequency in different lines in the Processors table.
To view disk performance and bandwidth in different lines, see the Performance and Bandwidth table.
HighFreq
A line of fixed configurations with an balanced vCPU:RAM ratio.
High-performance Enterprise-class equipment is used:
- Intel® Xeon® Gold 6354 processors (in pools ru-9, ru-2, ru-8, ke-1) or AMD EPYC 9474F (in pools ru-3, ru-7, uz-1). You can view the processor frequency in different lines in the Processors table;
- RAM ECC Reg 3.2 GHz (in pools ru-9, ru-2, ru-8, ke-1) or RAM DDR5 ECC Reg 4.8 GHz (in pools ru-3, ru-7, uz-1);
- High-performance SSD NVMe disks. To view disk performance and bandwidth in different lines, see the Performance and Bandwidth table.
Dedicated
A line of fixed configurations with cluster nodes on separate cloud servers. Each cloud server occupies an entire dedicated host (physical server). Suitable for users who need physical database isolation from other clients, maximum performance, and maximum available resource sizes.
High-performance Enterprise-class equipment is used:
- one Intel® Xeon® Gold 6336Y, Intel® Xeon® Gold 6240, Intel® Xeon® W-2255, or Intel® Xeon® E-2488 processor depending on the configuration. You can view the processor type and frequency for different lines in the Processors table;
- RAM 128 GB DDR4 ECC Reg, 64 GB DDR4 ECC Reg, or 32 GB DDR5 ECC Reg depending on the configuration;
- SSD NVMe disks in RAID 1. The number of disks in a cluster depends on the configuration. You can view disk performance and bandwidth for different lines in the Performance and bandwidth table;
- two 2 × 25 GE network cards for the main network + MC-LAG with a 25 Gbit/s connection speed for the service network (for backup, monitoring, and data replication in the cluster).
* DBMS clusters use Hyper-Threading Technology. Each physical core can process multiple threads in parallel—thanks to this, the total number of virtual cores (vCPU) exceeds the number of physical cores. This allows for more efficient load distribution during multi-threaded or analytical tasks.
** Part of the RAM is reserved for physical server service processes.
* ** Drives are combined into RAID 1 — a mirrored disk array that provides additional fault tolerance. When using mirroring, 50% of the total disk space is available for databases. A portion of the disk space is also reserved for physical server services.
Flex
A line of custom configurations with a local or network volume, in which you can choose the resource ratio.
You can view disk information in the Disks instruction.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. You can view the processor frequency in different lines in the Processors table.
To view configuration availability in regions, see the Managed Databases availability matrix. Configuration limits depend on the pool.
Local disk
Network volume
* If a configuration has more than 8 vCPUs, the vCPU:RAM ratio must be at least 1:4. For example, for 10 vCPUs, you need at least 40 GB of RAM.
** If a configuration has more than 8 vCPUs, the vCPU:Local disk ratio must be at least 1:32. For example, for 10 vCPUs, you need a disk of at least 320 GB.
If standard configurations do not suit your needs, you can order a custom one. Create a ticket and specify the resource ratio:
- vCPU:RAM — at least 1:4;
- vCPU:RAM:Local disk — at least 1:4:16.
Processors
Available processors vary by configuration line. Processor frequency affects the speed of processing user requests, executing complex algorithms, and data operations. Under 100% cloud server load, the processor operates using Turbo Boost technology. Since the processor is emulated, testing will show a lower frequency.
You can view the availability of configuration lines in regions in the Managed Databases availability matrix.