Redis versions and configurations
Versions
Redis version 6 is supported.
Node configurations
When creating a Redis 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.
When selecting a configuration, keep in mind that some disk space is reserved for service needs and is not available for databases. For more information, see Using disk space in a Redis cluster.
Once the cluster is created, you can change the configuration of nodes — scaling the cluster.
Configuration lines
The available node configurations are divided into ranges. The selected line of configurations depends on the processors and disks used.
In all line configurations, the resource ratio is fixed.
To see the availability of configurations in the regions, see the Cloud Databases availability matrix.
Standard
A line of fixed configurations with local disk and balanced vCPU:RAMratio, 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.
HighFreq
A line of fixed configurations with a balanced vCPU:RAMratio.
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® Gold 6240 (in Extra Large, Large and Medium configurations), Intel® Xeon® W-2255 (in Small configuration) or Intel® Xeon® E-2488 (in Extra Small and Micro configurations). To see the frequency of processors in different configuration lines, see the Processors table;
- RAM 64 GB DDR4 ECC Reg (in Extra Large, Large, Medium and Small configurations) or 32 GB DDR5 ECC Reg (in Extra Small and Micro configurations);
- 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).
* DBMS clusters use Hyper-Threading Technology. Each physical core can process several threads in parallel — due to this the total number of virtual cores (vCPU) exceeds the number of physical cores. This allows for more efficient load balancing for multi-threaded or analytical tasks.
** 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.
Processors
The fixed-configuration and random -configuration product lines differ in 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 runs with Turbo Boost technology. Since the processor is emulated, a lower frequency will be displayed during testing.
To see the availability of configurations in the regions, see the Cloud Databases availability matrix.