{
  "id": "hardware-requirements",
  "title": "Hardware requirements",
  "url": "https://redis.io/docs/latest/operate/rs/8.0/installing-upgrading/install/plan-deployment/hardware-requirements/",
  "summary": "Redis Software hardware requirements for development and production environments.",
  "content": "The hardware requirements for Redis Software are different for development and production environments.\n\n- In a development environment, you can test your application with a live database.\n\n    If you want to test your application under production conditions, use the production environment requirements.\n\n- In a production environment, you must have enough resources to handle the load on the database and recover from failures.\n\n## Architecture\n\nRedis Software supports AMD64 (x86_64) and ARM64 architectures as shown in the following table:\n\n| Operating system | AMD64 (x86_64) support | ARM64 support |\n|------------------|------------------------|---------------|\n| RHEL 9           | \u003cspan title=\"Supported\"\u003e:white_check_mark:\u003c/span\u003e Redis Software 7.4.2 and later | \u003cspan title=\"Supported\"\u003e:white_check_mark:\u003c/span\u003e Redis Software 8.0.10 and later |\n| RHEL 8           | \u003cspan title=\"Supported\"\u003e:white_check_mark:\u003c/span\u003e Redis Software 6.2.8 and later | \u003cspan title=\"Not supported\"\u003e:x:\u003c/span\u003e Not supported |\n| Ubuntu 22        | \u003cspan title=\"Supported\"\u003e:white_check_mark:\u003c/span\u003e Redis Software 7.8.4-66 and later | \u003cspan title=\"Supported\"\u003e:white_check_mark:\u003c/span\u003e Redis Software 8.0.10 and later |\n| Ubuntu 20        | \u003cspan title=\"Supported\"\u003e:white_check_mark:\u003c/span\u003e Redis Software 6.4.2-43 and later | \u003cspan title=\"Not supported\"\u003e:x:\u003c/span\u003e Not supported |\n| Amazon Linux 2   | \u003cspan title=\"Supported\"\u003e:white_check_mark:\u003c/span\u003e Redis Software 6.4.2-69 and later | \u003cspan title=\"Not supported\"\u003e:x:\u003c/span\u003e Not supported |\n\n## Development environment\n\nYou can build your development environment with non-production hardware, such as a laptop, desktop, or small VM or instance,\nand with these hardware requirements:\n\n| Item | Description | Minimum requirements | Recommended |\n|------------|-----------------|------------|-----------------|\n| Nodes per cluster | You can install on one node but many features require at least two nodes. | 1 node | \u003e= 2 nodes |\n| RAM per node | The amount of RAM for each node. | 4GB | \u003e= 10GB |\n| Storage per node | The amount of storage space for each node. | 10GB | \u003e= 20GB |\n\n## Production environment\n\nWe recommend these hardware requirements for production systems or for development systems that are designed to demonstrate production use cases:\n\n| Item | Description | Minimum requirements | Recommended |\n|------------|-----------------|------------|-----------------|\n| Nodes\u003csup\u003e[1](#table-note-1)\u003c/sup\u003e 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 | \u003e= 3 nodes (Must be an odd number of nodes) |\n| Cores\u003csup\u003e[2](#table-note-2)\u003c/sup\u003e per node | Redis 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 | \u003e=8 cores |\n| RAM\u003csup\u003e[3](#table-note-3)\u003c/sup\u003e per node | Defining your RAM size must be part of the capacity planning for your Redis usage. | 8GB | \u003e=32GB |\n| Ephemeral storage | Used for storing [replication files (RDB format) and cluster log files](https://redis.io/docs/latest/operate/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage). | RAM x 2 | \u003e= RAM x 4 |\n| Persistent storage\u003csup\u003e[4](#table-note-4)\u003c/sup\u003e | Used for storing [snapshot (RDB format) and AOF files](https://redis.io/docs/latest/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 \u003e= RAM x 4 (except for [extreme 'write' scenarios](https://redis.io/docs/latest/operate/rs/clusters/optimize/disk-sizing-heavy-write-scenarios))\u003cbr /\u003e\u003cbr /\u003e [Redis Flex and Auto Tiering](https://redis.io/docs/latest/operate/rs/databases/flash/) \u003e= (RAM + Flash) x 4. |\n| Network\u003csup\u003e[5](#table-note-5)\u003c/sup\u003e | We recommend using multiple NICs per node where each NIC is \u003e1Gbps, but Redis Software can also run over a single 1Gbps interface network used for processing application requests, inter-cluster communication, and storage access. | 1G | \u003e=10G |\n| Local disk for [Redis Flex and Auto Tiering](https://redis.io/docs/latest/operate/rs/databases/flash/) | used to to extend databases DRAM capacity with solid state drives (SSDs). Flash memory must be locally attached. [Read more](https://redis.io/docs/latest/operate/rs/databases/flash/) | (RAM+Flash) x 1.6 | (RAM+Flash) x 2.5 |\n\n\nAdditional considerations:\n\n1. \u003ca name=\"table-note-1\"\u003e\u003c/a\u003eNodes per cluster:\n\n    - Clusters with more than 35 nodes are not supported. Please contact the Redis support team for assistance if your sizing calls for deploying a larger number of nodes.\n\n    - Quorum nodes also must comply with the above minimal hardware requirements.\n    \n    - To ensure synchronization and consistency, Active-Active deployments with three-node clusters should not use quorum nodes. Because quorum nodes do not store data shards, they cannot support replication. In case of a node failure, replica shards aren't available for Active-Active synchronization.\n\n2. \u003ca name=\"table-note-2\"\u003e\u003c/a\u003eCores:\n\n    - When the CPU load reaches a certain level, Redis Software sends an alert to the operator.  \n\n    - If your application is designed to put a lot of load on your Redis database, make sure that you have at least one available core for each shard of your database.\n\n    - If some of the cluster nodes are utilizing more than 80% of the CPU, consider migrating busy resources to less busy nodes.\n\n    - If all the cluster nodes are utilizing over 80% of the CPU, highly consider scaling out the cluster by [adding a node](https://redis.io/docs/latest/operate/rs/clusters/add-node).\n\n3. \u003ca name=\"table-note-3\"\u003e\u003c/a\u003e RAM:\n\n    - 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.\n\n    - If one or more cluster nodes utilizes more than 65% of the RAM, consider migrating resources to less active nodes.\n\n    - If all cluster nodes are utilizing more than 70% of available RAM, highly consider [adding a node](https://redis.io/docs/latest/operate/rs/clusters/add-node).\n\n    - Do not run any other memory-intensive processes on the Redis Software node.\n\n4. \u003ca name=\"table-note-4\"\u003e\u003c/a\u003ePersistent storage:\n\n    - If no databases on the cluster have [persistence](https://redis.io/docs/latest/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 Software also uses it to maintain the cluster and database health, configurations, recovery procedures, and more.\n  \n5. \u003ca name=\"table-note-5\"\u003e\u003c/a\u003eNetwork:\n\n    - Only static IP addresses are supported to ensure nodes remain part of the cluster after a reboot.\n\n\n\n## Sizing considerations\n\n### General database sizing {#general-sizing}\n\nFactors to consider when sizing your database.\n\n- **Dataset size** – Your limit should be greater than your dataset size to leave room for overhead.\n- **Database throughput** – High throughput needs more shards, leading to a higher memory limit.\n- [**Modules**](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise) – Using modules with your database consumes more memory.\n- [**Database clustering**](https://redis.io/docs/latest/operate/rs/databases/durability-ha/clustering) – Allows you to spread your data into shards across multiple nodes.\n- [**Database replication**](https://redis.io/docs/latest/operate/rs/databases/durability-ha/replication) – Enabling replication doubles memory consumption.\n\n### Active-Active database sizing {#active-active-sizing}\n\nAdditional factors for sizing Active-Active databases:\n\n- [**Active-Active replication**](https://redis.io/docs/latest/operate/rs/databases/active-active) – Requires double the memory of regular replication, which can be up to two times (2x) the original data size per instance.\n- [**Database replication backlog**](https://redis.io/docs/latest/operate/rs/databases/durability-ha/replication#database-replication-backlog) – For synchronization between shards. By default, this is set to 1% of the database size.\n- [**Active-Active replication backlog**](https://redis.io/docs/latest/operate/rs/databases/active-active/manage#replication-backlog) – For synchronization between clusters. By default, this is set to 1% of the database size.\n\n\nActive-Active databases have a lower threshold for activating the eviction policy, because it requires propagation to all participating clusters. The eviction policy starts to evict keys when one of the Active-Active instances reaches 80% of its memory limit.\n\n\n### Sizing databases with Auto Tiering enabled  {#redis-on-flash-sizing}\n\nAdditional factors for sizing  databases with Auto Tiering enabled:\n\n- [**Database persistence**](https://redis.io/docs/latest/operate/rs/databases/configure/database-persistence#redis-on-flash-data-persistence) – Auto Tiering uses dual database persistence where both the primary and replica shards persist to disk. This may add some processor and network overhead, especially in cloud configurations with network-attached storage.\n\n",
  "tags": ["docs","operate","rs","kubernetes"],
  "last_updated": "2026-07-23T12:05:56-05:00"
}