Prompt

Why is my Redis cache getting evicted so fast?

Technology / Cloud Infrastructure2 observationsLast seen Nov 15, 2026

Latest observation

Nov 15, 2026OpenAI APIWeb search: off

“Evicted so fast” in Redis usually means Redis is running out of memory and is actively removing keys according to its eviction policy, or your keys are expiring sooner than you expect. The most common causes are:

1) Memory limit is too low

If maxmemory is set too small, Redis will start evicting keys once it reaches that limit.

Check:

redis-cli INFO memory
redis-cli CONFIG GET maxmemory

2) Eviction policy is aggressive

Redis evicts keys based on maxmemory-policy when memory is full. Common policies:

  • allkeys-lru: evicts least recently used keys
  • volatile-lru: evicts only keys with TTL
  • allkeys-random: evicts random keys
  • volatile-ttl: evicts keys with nearest expiry

Check:

redis-cli CONFIG GET maxmemory-policy

3) Your keys have TTLs and are expiring normally

Sometimes what looks like eviction is just expiration.

Check stats:

redis-cli INFO stats

Look at:

  • expired_keys
  • evicted_keys

If expired_keys is rising, the keys are timing out.
If evicted_keys is rising, Redis is removing them due to memory pressure.

4) Memory usage is higher than expected

Possible reasons:

  • Large values
  • Too many keys
  • Inefficient data structures
  • Overhead from lots of small keys
  • Replication/AOF/RDB memory overhead

Inspect:

redis-cli MEMORY STATS
redis-cli DBSIZE
redis-cli --bigkeys

5) Some client is overwriting or deleting keys

Application bugs, cleanup jobs, or cache invalidation logic can make it seem like Redis is evicting keys.

Check key access and deletions in app logs, or temporarily monitor:

redis-cli MONITOR

6) Container / VM memory pressure

If Redis is in Docker/Kubernetes/limited VM memory, the host may be under pressure, causing instability or forced evictions depending on setup.

Check:

  • container memory limit
  • host RAM usage
  • Redis used_memory_rss

Fastest way to diagnose

Run these commands:

redis-cli INFO stats
redis-cli INFO memory
redis-cli CONFIG GET maxmemory
redis-cli CONFIG GET maxmemory-policy

Then compare:

  • evicted_keys
  • expired_keys
  • used_memory
  • maxmemory

If you want, paste the output of:

redis-cli INFO stats
redis-cli INFO memory
redis-cli CONFIG GET maxmemory
redis-cli CONFIG GET maxmemory-policy

and I can tell you exactly why it’s happening.

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (2 observations for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.