From d9770346c435909bfc738e9dff322d03239b21f1 Mon Sep 17 00:00:00 2001 From: Alon Magrafta <50071256+AlonMagrafta@users.noreply.github.com> Date: Wed, 22 Jan 2025 18:14:20 +0200 Subject: [PATCH] Update hardware-requirements-embed.md (#1078) * Update hardware-requirements-embed.md update SW min hardware requirements add Redis Flex (auto tiering) min local disk size requirements * Update hardware-requirements-embed.md min HW requirements when no persistency used * Small style updates for sentence case * Update content/embeds/hardware-requirements-embed.md Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> * Update content/embeds/hardware-requirements-embed.md Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> * Update hardware-requirements-embed.md * Update hardware-requirements-embed.md * Added footnote link to persistent storage row & updated footnote order --------- Co-authored-by: Rachel Elledge Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> --- content/embeds/hardware-requirements-embed.md | 23 ++++++++++++------- 1 file changed, 15 insertions(+), 8 deletions(-) diff --git a/content/embeds/hardware-requirements-embed.md b/content/embeds/hardware-requirements-embed.md index 6bd7d54c2..321d8f172 100644 --- a/content/embeds/hardware-requirements-embed.md +++ b/content/embeds/hardware-requirements-embed.md @@ -24,11 +24,13 @@ We recommend these hardware requirements for production systems or for developme | Item | Description | Minimum requirements | Recommended | |------------|-----------------|------------|-----------------| | Nodes[1](#table-note-1) per cluster | At least three nodes are required to support a reliable, highly available deployment that handles process failure, node failure, and network split events in a consistent manner. | 3 nodes | >= 3 nodes (Must be an odd number of nodes) | -| Cores[2](#table-note-2) per node | Redis Enterprise Software is based on a multi-tenant architecture and can run multiple Redis processes (or shards) on the same core without significant performance degradation. | 4 cores | >=8 cores | -| RAM[3](#table-note-3) per node | Defining your RAM size must be part of the capacity planning for your Redis usage. | 15GB | >=30GB | -| Ephemeral Storage | Used for storing [replication files (RDB format) and cluster log files]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}). | RAM x 2 | >= RAM x 4 | -| Persistent Storage | Used for storing [snapshot (RDB format) and AOF files]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}) over a persistent storage media, such as AWS Elastic Block Storage (EBS) or Azure Data Disk. | RAM x 3 | In-memory >= RAM x 6 (except for [extreme 'write' scenarios]({{< relref "/operate/rs/clusters/optimize/disk-sizing-heavy-write-scenarios" >}}))

[Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}}) >= (RAM + Flash) x 5. | -| Network[4](#table-note-4) | We recommend using multiple NICs per node where each NIC is >100Mbps, but Redis Enterprise Software can also run over a single 1Gbps interface network used for processing application requests, inter-cluster communication, and storage access. | 1G | >=10G | +| Cores[2](#table-note-2) per node | Redis Enterprise Software is based on a multi-tenant architecture and can run multiple Redis processes (or shards) on the same core without significant performance degradation. | 2 cores | >=8 cores | +| RAM[3](#table-note-3) per node | Defining your RAM size must be part of the capacity planning for your Redis usage. | 8GB | >=32GB | +| Ephemeral storage | Used for storing [replication files (RDB format) and cluster log files]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}). | RAM x 2 | >= RAM x 4 | +| Persistent storage[4](#table-note-4) | Used for storing [snapshot (RDB format) and AOF files]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}) over a persistent storage media, such as AWS Elastic Block Storage (EBS) or Azure Data Disk. | RAM x 3 | In-memory >= RAM x 4 (except for [extreme 'write' scenarios]({{< relref "/operate/rs/clusters/optimize/disk-sizing-heavy-write-scenarios" >}}))

[Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}}) >= (RAM + Flash) x 4. | +| Network[5](#table-note-5) | We recommend using multiple NICs per node where each NIC is >1Gbps, but Redis Enterprise Software can also run over a single 1Gbps interface network used for processing application requests, inter-cluster communication, and storage access. | 1G | >=10G | +| Local disk for [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}}) | used to to extend databases DRAM capacity with solid state drives (SSDs). Flash memory must be locally attached. [Read more]({{< relref "/operate/rs/databases/auto-tiering/" >}}) | (RAM+Flash) x 1.6 | (RAM+Flash) x 2.5 | + Additional considerations: @@ -48,7 +50,7 @@ Additional considerations: - If some of the cluster nodes are utilizing more than 80% of the CPU, consider migrating busy resources to less busy nodes. - - If all the cluster nodes are utilizing over 80% of the CPU, consider scaling out the cluster by [adding a node]({{< relref "/operate/rs/clusters/add-node" >}}). + - If all the cluster nodes are utilizing over 80% of the CPU, highly consider scaling out the cluster by [adding a node]({{< relref "/operate/rs/clusters/add-node" >}}). 3. RAM: @@ -56,10 +58,15 @@ Additional considerations: - If one or more cluster nodes utilizes more than 65% of the RAM, consider migrating resources to less active nodes. - - If all cluster nodes are utilizing more than 70% of available RAM, consider [adding a node]({{< relref "/operate/rs/clusters/add-node" >}}). + - If all cluster nodes are utilizing more than 70% of available RAM, highly consider [adding a node]({{< relref "/operate/rs/clusters/add-node" >}}). - Do not run any other memory-intensive processes on the Redis Enterprise Software node. -4. Network: +4. Persistent storage: + + - If no databases on the cluster have [persistence]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}) enabled, minimum persistent storage is RAM x 1.1 and the recommended persistent storage is RAM x 2. Persistent storage is essential because Redis Enterprise also uses it to maintain the cluster and database health, configurations, recovery procedures, and more. + +5. Network: - Only static IP addresses are supported to ensure nodes remain part of the cluster after a reboot. +