From 04ef12ea595ca4b451efe361616c64d1cd457321 Mon Sep 17 00:00:00 2001 From: Alon Magrafta <50071256+AlonMagrafta@users.noreply.github.com> Date: Tue, 21 Jan 2025 13:35:44 +0200 Subject: [PATCH 1/8] Update hardware-requirements-embed.md update SW min hardware requirements add Redis Flex (auto tiering) min local disk size requirements --- content/embeds/hardware-requirements-embed.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/content/embeds/hardware-requirements-embed.md b/content/embeds/hardware-requirements-embed.md index 6bd7d54c2..efa640b21 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 | +| 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 | 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 | +| 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 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[4](#table-note-4) | 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,7 +58,7 @@ 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. From 93342305b93ad05910418fe3eb5571089f0be248 Mon Sep 17 00:00:00 2001 From: Alon Magrafta <50071256+AlonMagrafta@users.noreply.github.com> Date: Tue, 21 Jan 2025 13:41:59 +0200 Subject: [PATCH 2/8] Update hardware-requirements-embed.md min HW requirements when no persistency used --- content/embeds/hardware-requirements-embed.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/content/embeds/hardware-requirements-embed.md b/content/embeds/hardware-requirements-embed.md index efa640b21..5e2f14f6c 100644 --- a/content/embeds/hardware-requirements-embed.md +++ b/content/embeds/hardware-requirements-embed.md @@ -61,7 +61,12 @@ Additional considerations: - 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. + +3. RAM: -4. Network: + - Redis uses a relatively large number of buffers, which enable replica communication, client communication, pub/sub commands, and more. As a result, you should ensure that 30% of the RAM is available on each node at any given time. + + +4. Persistent Storage: - - Only static IP addresses are supported to ensure nodes remain part of the cluster after a reboot. + - When all databases on the cluster do not use, and will not enable [persistency]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}), minimal Persistent Storage can be lowered to RAM x 1.1 and recommended to RAM x 2. Having a Persistent Storage is essencial as it's being used also by Redis Enteprise to maintain the cluster and database health, configurations, recovery procedures and more. From 0ed4107070c6232982a0d310248008e117c294e0 Mon Sep 17 00:00:00 2001 From: Rachel Elledge Date: Tue, 21 Jan 2025 09:51:56 -0600 Subject: [PATCH 3/8] Small style updates for sentence case --- content/embeds/hardware-requirements-embed.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/embeds/hardware-requirements-embed.md b/content/embeds/hardware-requirements-embed.md index 5e2f14f6c..e0337ee71 100644 --- a/content/embeds/hardware-requirements-embed.md +++ b/content/embeds/hardware-requirements-embed.md @@ -26,8 +26,8 @@ We recommend these hardware requirements for production systems or for developme | 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. | 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 | 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. | +| 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 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[4](#table-note-4) | 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 | @@ -67,6 +67,6 @@ Additional considerations: - Redis uses a relatively large number of buffers, which enable replica communication, client communication, pub/sub commands, and more. As a result, you should ensure that 30% of the RAM is available on each node at any given time. -4. Persistent Storage: +4. Persistent storage: - When all databases on the cluster do not use, and will not enable [persistency]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}), minimal Persistent Storage can be lowered to RAM x 1.1 and recommended to RAM x 2. Having a Persistent Storage is essencial as it's being used also by Redis Enteprise to maintain the cluster and database health, configurations, recovery procedures and more. From 5f1ba6c086866a49660bc5939ea8838733a0ad0c Mon Sep 17 00:00:00 2001 From: Alon Magrafta <50071256+AlonMagrafta@users.noreply.github.com> Date: Wed, 22 Jan 2025 15:24:26 +0200 Subject: [PATCH 4/8] Update content/embeds/hardware-requirements-embed.md Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> --- content/embeds/hardware-requirements-embed.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/content/embeds/hardware-requirements-embed.md b/content/embeds/hardware-requirements-embed.md index e0337ee71..55b2af198 100644 --- a/content/embeds/hardware-requirements-embed.md +++ b/content/embeds/hardware-requirements-embed.md @@ -61,11 +61,6 @@ Additional considerations: - 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. - -3. RAM: - - - Redis uses a relatively large number of buffers, which enable replica communication, client communication, pub/sub commands, and more. As a result, you should ensure that 30% of the RAM is available on each node at any given time. - 4. Persistent storage: From 80e09eff6723143d35a13ca0bb17c2e6157e2d05 Mon Sep 17 00:00:00 2001 From: Alon Magrafta <50071256+AlonMagrafta@users.noreply.github.com> Date: Wed, 22 Jan 2025 15:24:54 +0200 Subject: [PATCH 5/8] Update content/embeds/hardware-requirements-embed.md Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> --- content/embeds/hardware-requirements-embed.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/embeds/hardware-requirements-embed.md b/content/embeds/hardware-requirements-embed.md index 55b2af198..705ece806 100644 --- a/content/embeds/hardware-requirements-embed.md +++ b/content/embeds/hardware-requirements-embed.md @@ -64,4 +64,4 @@ Additional considerations: 4. Persistent storage: - - When all databases on the cluster do not use, and will not enable [persistency]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}), minimal Persistent Storage can be lowered to RAM x 1.1 and recommended to RAM x 2. Having a Persistent Storage is essencial as it's being used also by Redis Enteprise to maintain the cluster and database health, configurations, recovery procedures and more. + - 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. From d8031fcae16e5ddb120afcda6dc47a7b5ef6075a Mon Sep 17 00:00:00 2001 From: Alon Magrafta <50071256+AlonMagrafta@users.noreply.github.com> Date: Wed, 22 Jan 2025 15:27:21 +0200 Subject: [PATCH 6/8] Update hardware-requirements-embed.md --- content/embeds/hardware-requirements-embed.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/content/embeds/hardware-requirements-embed.md b/content/embeds/hardware-requirements-embed.md index 705ece806..aa884fb5a 100644 --- a/content/embeds/hardware-requirements-embed.md +++ b/content/embeds/hardware-requirements-embed.md @@ -61,7 +61,11 @@ Additional considerations: - 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: + - Only static IP addresses are supported to ensure nodes remain part of the cluster after a reboot. + +6. 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. From fe55d8cc2b73d2c2e42fd2c7d3779df6ac3c8441 Mon Sep 17 00:00:00 2001 From: Alon Magrafta <50071256+AlonMagrafta@users.noreply.github.com> Date: Wed, 22 Jan 2025 15:29:04 +0200 Subject: [PATCH 7/8] Update hardware-requirements-embed.md --- content/embeds/hardware-requirements-embed.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/embeds/hardware-requirements-embed.md b/content/embeds/hardware-requirements-embed.md index aa884fb5a..6f67cc40f 100644 --- a/content/embeds/hardware-requirements-embed.md +++ b/content/embeds/hardware-requirements-embed.md @@ -62,7 +62,7 @@ Additional considerations: - Do not run any other memory-intensive processes on the Redis Enterprise Software node. -4. Network: +4. Network: - Only static IP addresses are supported to ensure nodes remain part of the cluster after a reboot. From 44f3f880b6f09f6a9d0783895be692fa215219b1 Mon Sep 17 00:00:00 2001 From: Rachel Elledge Date: Wed, 22 Jan 2025 10:02:52 -0600 Subject: [PATCH 8/8] Added footnote link to persistent storage row & updated footnote order --- content/embeds/hardware-requirements-embed.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/content/embeds/hardware-requirements-embed.md b/content/embeds/hardware-requirements-embed.md index 6f67cc40f..321d8f172 100644 --- a/content/embeds/hardware-requirements-embed.md +++ b/content/embeds/hardware-requirements-embed.md @@ -27,8 +27,8 @@ We recommend these hardware requirements for production systems or for developme | 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 | 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[4](#table-note-4) | 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 | +| 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 | @@ -61,11 +61,12 @@ Additional considerations: - 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: - - Only static IP addresses are supported to ensure nodes remain part of the cluster after a reboot. +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: -6. Persistent storage: + - Only static IP addresses are supported to ensure nodes remain part of the cluster after a reboot. - - 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.