MySQL sync versions and configurations
Versions
MySQL sync version 8 is supported.
Node configurations
When creating a MySQL sync cloud database cluster, you can select the configuration of nodes — number of vCPUs, RAM, and disk size.
The available node configurations are divided into ranges. The selected line of configurations depends on the processors and disks used.
When selecting a configuration, consider that about 5 GB of disk space in all configurations is reserved for the operating system, service components, and log storage. The rest of the disk space is available for databases.
Once the cluster is created, you can change the configuration of nodes — scaling the cluster.
Configuration lines
The ratio of resources in line configurations can be:
To see the availability of configuration lineups in the regions, see the Cloud Databases availability matrix.
Standard
A line of fixed configurations with local disk and balanced vCPU:RAM ratio, suitable for most DBMSs. We recommend using this lineup if you do not know the load profile.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. See the Processors table to view the processor frequencies of the different configuration lines.
See the Performance and Throughput table to see the performance and throughput of the drives in the different product lines.
CPU
A line of fixed configurations with local disk and balanced vCPU:RAM ratio. Suitable for workload profiles that are computationally demanding. For example, if the database is running analytic queries, multiple nested queries, or data encryption. One way to determine such a load 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. See the Processors table to view the processor frequencies of the different configuration lines.
See the Performance and Throughput table to see the performance and throughput of the drives in the different product lines.
Memory
A line of fixed configurations with local disk and balanced vCPU:RAM ratio. Suitable for workload profiles that are cache-intensive. For example, if the database runs multiple, infrequent queries on different parts of tables. One way to determine such a load profile is to monitor the metric Cash_hit_ratio, which shows the percentage of data in a query that is read from the cache.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. See the Processors table to view the processor frequencies of the different configuration lines.
See the Performance and Throughput table to see the performance and throughput of the drives in the different product lines.
HighFreq
A line of fixed configurations with a balanced vCPU:RAM ratio.
High-performance Enterprise-level 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). To see the frequency of processors in different configuration lines see 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);
- SSD NVMe disks with higher performance. See the Performance and Throughput table to see the performance and throughput of the drives in the different product lines.
Dedicated
A line of fixed configurations with cluster nodes on separate cloud servers. Each cloud server occupies the entire dedicated host (physical server). Suitable for users who require physical isolation of databases from other clients, maximum performance and maximum size of available resources.
High-performance Enterprise-level equipment is used:
- one Intel® Xeon® W-2255 (Small configuration) or Intel® Xeon® Gold 6240 (Medium, Large, and Extra Large configurations). To see the frequency of processors in different configuration lines, see the Processors table;
- RAM 64 GB DDR4 ECC Reg;
- two SSD NVMe disks in RAID 1. To see the performance and throughput of the drives in different lines, see the Performance and Throughput table;
- two 2 × 25 GE NICs for the main network + MC-LAG with 25 Gbps connection speed for the service network (for backup, monitoring, data replication in the cluster).
* To improve the performance of the DBMS cluster, Hyper-Threading Technology is used. This technology allows you to use 34 vCPUs on top of the physical 18 CPUs. This performance is suitable for highly loaded systems or analytical load profile.
** One slate of RAM is reserved for the services that maintain the physical server.
* ** To provide additional fault tolerance, the disks are placed in RAID 1. This is a mirrored disk array, so 50% of the disk space is available for the database. Part of the disk space is also reserved for services that maintain the physical server.
Flex
A line of arbitrary configurations with local or network disk, in which you can choose the resource ratio.
To see information about the disks, see the Disks manual.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. See the Processors table to view the processor frequencies of the different configuration lines.
To see the availability of configurations in the regions, see the Cloud Databases availability matrix. Configuration limits depend on the pool.
Local disk
Network disk
* If there are more than 8 vCPUs in a configuration, the vCPU:RAM ratio must be at least 1:4. For example, 10 vCPUs require at least 40 GB of RAM.
** If the configuration has more than 8 vCPUs, the vCPU:Local Disk ratio must be at least 1:32. For example, 10 vCPUs require a disk size of at least 320 GB.
If the configurations are not suitable, you can order your own configuration. Create a ticket and specify the resource ratio:
- vCPU:RAM — at least 1:4;
- vCPU:RAM:Local disk — at least 1:4:16.
Processors
Configuration lines differ in the available processors. Processor frequency affects the speed of processing user requests, performing complex algorithms and data operations. When the cloud server load is 100%, the processor is running Turbo Boost technology. Since the processor is emulated, a lower frequency will be displayed during testing.
To see the availability of configuration lineups in the regions, see the Cloud Databases availability matrix.