How much memory I need for Redis?

The amount of memory you need for Redis depends on several factors, such as the size of your WordPress site, the amount of traffic, and the caching strategy you plan to use. Here’s a breakdown of how to estimate your memory needs:

1. Determine What You’ll Be Caching

• Object Cache: If you’re only caching frequently accessed database queries (object cache), you may not need a large amount of memory. For small to medium sites, 256 MB to 512 MB is often enough. For larger sites or those with high database usage, consider 512 MB to 1 GB.
• Page Cache: Caching full pages requires more memory, as each cached page can take up several kilobytes or more, depending on the page’s content. If you plan to cache full pages, start with 1 GB of memory. Larger sites may need 2 GB or more, especially if there’s a lot of dynamic content.
• Session Cache: For sites with user sessions (e.g., WooCommerce or membership sites), you’ll need enough memory to store user session data. This is generally low, so 128 MB to 256 MB can often be sufficient, even for larger sites.

2. Estimate Data Size Based on Site Traffic and Cache TTL

• Traffic: High-traffic sites require more memory because they’ll cache more frequently accessed pages and objects. For example, if you receive 10,000+ visitors per day, you might want to allocate 1 GB or more to Redis.
• Time-to-Live (TTL): Cache TTL defines how long items stay in Redis before being evicted. Shorter TTLs mean less memory usage, while longer TTLs can require more memory. With a TTL of 10 minutes for pages, you might get by with less memory. If you want to cache pages for an hour or longer, you’ll need additional space.

3. Estimate for WooCommerce or Larger Sites

• For a WooCommerce site with a larger catalog and high traffic, 2 GB to 4 GB of memory is often needed. WooCommerce sites have more dynamic data to cache, such as product details, shopping cart contents, and user sessions.
• For enterprise or large-scale sites, you might need 4 GB+ depending on your caching needs and the size of the site.

4. Use a Formula to Estimate Memory

If you’d like a more specific estimate, you can use a formula based on the number of cached items, the average size of each item, and the overhead. For example:

• Estimate the number of items to be cached per day.
• Average item size: If each cached page or object averages around 10 KB, multiply by the number of items.
• Memory overhead: Add about 20% to 30% overhead for Redis to manage the cache.

Here’s a rough formula: Memory (MB)=Total Items×Average Item Size (KB)×1.3/​₁₀₂₄

5. Monitor and Adjust as Needed

Start with a reasonable estimate (e.g., 1 GB for a medium-sized site) and monitor your Redis memory usage using tools like redis-cli or a monitoring dashboard (like Datadog or RedisInsight). If you notice Redis is running out of memory frequently, you may need to increase it.

Sample Estimates

• Small Site (Low Traffic, Object Cache Only): ~256 MB to 512 MB
• Medium Site (Moderate Traffic, Object + Page Cache): ~512 MB to 1 GB
• Large Site or WooCommerce Site (High Traffic, Full Cache): ~2 GB to 4 GB
• Enterprise Site (Very High Traffic, Custom Caching Requirements): 4 GB+

By monitoring and fine-tuning based on your site’s actual usage, you can determine the most efficient amount of memory for Redis to improve your WordPress site’s performance.

But hosting provider’s offers starts from 32MB, why I see such options 32MB, 64MB, 128MB if you even don’t consider them?

You’re right that some hosting providers offer Redis options starting as low as 32 MB or 64 MB. These smaller configurations are often available because they can still be useful for certain scenarios, particularly for low-traffic sites or very specific caching tasks. Here’s why smaller memory allocations might still be relevant and when they could be suitable:

1. Basic Caching Needs for Low-Traffic Sites

• For small blogs or personal sites with low traffic, 32 MB or 64 MB may be enough to cache a few objects or database query results, especially if you’re only using Redis for simple object caching.
• Smaller Redis instances work well for sites that don’t have complex caching needs and just need to offload some database queries to reduce server load.

2. Short-Lived Caching for Faster Page Loads

• If you set short TTLs (like a few minutes) for cached data, 32 MB can be sufficient for temporarily storing a limited number of objects or pages. This way, you benefit from faster page loads even on a budget.
• This can be helpful for local development environments or testing, where performance requirements are less demanding.

3. Single-Purpose Caching

• Session caching for a small site, such as a small e-commerce store or membership site, might only require 32 MB to 64 MB if you have limited concurrent users. If you only use Redis to store user sessions, small amounts of memory can handle this task without significant strain.
• For very specific caching tasks, such as API response caching for a few select queries, small allocations can work if the data volume is limited.

4. Light Object Caching for WordPress Core

• Even a small amount of Redis memory can help reduce database calls for the WordPress core data that doesn’t change often, such as site options, widget settings, and menu structures. For these lightweight items, 64 MB might be enough for very basic optimization.

5. Redis as a Supplement, Not a Full Solution

• For some setups, Redis is used as a supplemental caching layer alongside other caching solutions. For example, Redis might handle transient caching, while a plugin like WP Rocket handles full-page caching. In such cases, you might only need 32 MB or 64 MB for Redis.

Practical Example: 32 MB or 64 MB Usage Scenario

Let’s say you have a low-traffic blog or personal site that mainly caches:

• Site options
• User sessions for a small number of logged-in users
• Temporary transients (like API data for a small weather widget)

For this limited usage, 32 MB or 64 MB may handle your requirements, especially if the cached data has a short lifespan and is refreshed frequently.

However, if you anticipate scaling or you’re running a commercial website that’s expected to handle more traffic, starting with 128 MB to 256 MB or higher is generally a better long-term approach.

In summary, while 32 MB or 64 MB of Redis can indeed be useful for certain lightweight tasks or smaller websites, larger allocations are recommended for sites that expect higher traffic, need to cache more data, or want to optimize performance more comprehensively.