# Non-Graviton ElastiCache node on eligible workload Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/non-graviton-elasticache-node-on-eligible-workload Many Redis and Memcached clusters still use legacy x86-based node types (e.g., cache.r5, cache.m5) even though Graviton-based alternatives are available. By: Loïc Fournier Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Non-Graviton ElastiCache Node on Eligible Workload The short version Many Redis and Memcached clusters still use legacy x86-based node types (e.g., cache.r5, cache.m5) even though Graviton-based alternatives are available. [Loïc Fournier](https://www.linkedin.com/in/loicfournier/) Senior TAM @ Amazon Web Services AWS service [AWS ElastiCache](https://www.pointfive.co/efficiency-hub/cloud-services/aws-elasticache) Category [Databases](https://www.pointfive.co/efficiency-hub/service-category/databases) Reference CER-0146 Type Suboptimal Tier or SKU ## Explanation Why the waste happens and who it affects. In-memory workloads tend to be highly compatible with Graviton due to their simplicity and reliance on standard CPU and memory usage patterns.Unless constrained by architecture-specific extensions or strict compliance requirements, most ElastiCache clusters can be transitioned with no application-level changes. Failing to migrate to Graviton results in unnecessary compute spend and missed opportunities to improve cache efficiency. ## Billing model The pricing dimensions that drive this cost. ElastiCache is billed hourly per node, based on: - Node type and size - Engine and region Per-hour prices for Graviton node types are close to those of comparable x86 node types (slightly lower for Graviton2, similar or slightly higher for newer Graviton generations). AWS cites up to 45% better price/performance for Graviton2 nodes compared with previous-generation nodes, so savings depend mainly on whether the workload can then run on fewer or smaller nodes. ## How to detect 4 checks to find it in your estate. - Enumerate all ElastiCache clusters and identify those using x86-based families - Cross-check with cache.\*g instance types available in the region and engine - Confirm that clusters have no known architecture-specific dependencies - Analyze memory and CPU usage patterns to validate fit with Graviton ## How to fix 4 ways to remove the waste. - Switch node types to current Graviton families supported for your engine and Region (e.g., cache.r8g/r7g, cache.m8g/m7g, cache.t4g, or cache.c8gn/c7gn) - Update provisioning logic to default to Graviton families for new clusters - Pilot in non-prod or lower-tier environments to validate behavior and latency - Incorporate architecture reviews into ElastiCache lifecycle and scaling workflows ## Documentation Vendor references for pricing and configuration. - [Supported node types docs.aws.amazon.com](https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/CacheNodes.SupportedTypes.html) - [AWS Graviton Processors aws.amazon.com](https://aws.amazon.com/ec2/graviton/) - [Amazon ElastiCache Pricing aws.amazon.com](https://aws.amazon.com/elasticache/pricing/) - [Amazon ElastiCache now supports M6g and R6g Graviton2-based instances aws.amazon.com](https://aws.amazon.com/about-aws/whats-new/2020/10/amazon-elasticache-now-supports-m6g-and-r6g-graviton2-based-instances/) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - AWS ElastiCache CER-0321 ### [Suboptimal Cache TTL Strategy Causing Repeated Backend Execution](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-cache-ttl-strategy-causing-repeated-backend-execution) Organizations deploy ElastiCache to reduce load on backend systems - databases, APIs, and compute layers - by serving frequently accessed data from fast in-memory storage. However, when Time-to-Live (TTL) values are misaligned with actual... Databases - AWS ElastiCache CER-0284 ### [Outdated ElastiCache Engine Version Incurring Extended Support Charges](https://www.pointfive.co/efficiency-hub/inefficiencies/outdated-elasticache-engine-version-incurring-extended-support-charges) ElastiCache clusters continue running engine versions that have moved into extended support. While the service remains functional, AWS charges an ongoing premium for extended support that provides no added performance or capability. These... Databases - AWS ElastiCache CER-0105 ### [Suboptimal ElastiCache Engine Selection](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-elasticache-engine-selection) Many workloads default to using Redis or Memcached without evaluating whether a lighter or more efficient engine would provide equivalent functionality at lower cost. Valkey is a Redis-compatible, open-source engine supported by... Databases --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.