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 part of the disk space is reserved for system purposes and is unavailable for hosting databases. For more information, see the Using disk space in a MySQL sync cluster instructions.
After creating a cluster, you can change the node configuration— scale the cluster.
Configuration lines
The resource ratio in configuration lines can be:
You can check the availability of configuration lineups across locations in the instructions on Cloud database availability by location.
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 check the processor frequency in different lineups in the table Processors.
You can check disk performance and throughput in different lineups in the table Performance and throughput.
CPU
A line of fixed configurations with a local disk and a balanced vCPU:RAM ratio. Suitable for compute-intensive workload profiles. For example, if analytical queries, multiple subqueries, or data encryption are run in the database. One way to determine such a workload profile is to track the metric Load Average, which shows the average system load over one, five, or 15 minutes.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. You can check the processor frequency in different lineups in the table Processors.
You can check disk performance and throughput in different lineups in the table Performance and throughput.
Memory
A line of fixed configurations with a local disk and a balanced vCPU:RAM ratio. Suitable for caching-demanding workload profiles. For example, if multiple, infrequently repeated queries to different parts of tables are executed in the database. One way to determine such a workload profile is to track the metric Попадание in кэш (Cache_hit_ratio), which shows the percentage of data in a query read from the cache.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. You can check the processor frequency in different lineups in the table Processors.
You can check disk performance and throughput in different lineups in the table Performance and throughput.
HighFreq
A line of fixed configurations with an balanced vCPU:RAM ratio.
High-performance Enterprise-class equipment is used:
- processors Intel® Xeon® Gold 6354 (in pools ru-9, ru-2, ru-8, ke-1) or AMD EPYC 9474F (in pools ru-3, ru-7, uz-1, and uz-2). You can view processor frequencies in different lineups in the table Processors;
- 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, and uz-2);
- High-performance NVMe SSDs. You can check disk performance and throughput in different lineups in the table Performance and throughput.
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 check the processor type and frequency in different lineups in the table Processors;
- RAM 128 GB DDR4 ECC Reg, 64 GB DDR4 ECC Reg, or 32 GB DDR5 ECC Reg depending on the configuration;
- NVMe SSDs in RAID 1. The number of disks in a cluster depends on the configuration. You can check disk performance and throughput in different lineups in the table Performance and throughput;
- 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 multithreaded or analytical tasks.
** Part of the RAM is reserved for physical server services.
* ** Disks are combined into RAID 1 — a mirrored disk array that provides additional fault tolerance. When using mirroring, 50% of total disk space is available for databases. Part 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 instructions on Disks.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. You can check the processor frequency in different lineups in the table Processors.
Configuration limits depend on the location.
Local disk
Network volume
* The vCPU:RAM ratio must be at least 1:2:
- for clusters in the ru-6 pool;
- for clusters in other pools if the configuration has more than 8 vCPUs.
For example, for 10 vCPUs, you need at least 20 GB of RAM.
** The vCPU:Local disk ratio must be:
- at least 1:32 for clusters in the ru-1 pool if the configuration has more than 8 vCPUs. For example, for 10 vCPUs, you need a disk of at least 320 GB;
- at least 1:16 for clusters in the ru-6 pool. For example, for 10 vCPUs, you need a disk of at least 160 GB;
- at least 1:16 for clusters in all pools except ru-1 and ru-6 if the configuration has more than 8 vCPUs.
If the configurations do not suit your needs, you can order a custom configuration. Create a ticket and specify the resource ratio.
Processors
Different configuration lineups offer different processors. The processor frequency affects how quickly user requests are processed, how complex algorithms are executed, and how data operations are performed. When a cloud server is at 100% load, the processor uses Turbo Boost technology. Since the processor is virtualized, testing will show a lower frequency.