Redis Production Checklist

maxmemory is set, and it leaves headroom below the host or container limit for replication buffers and copy-on-write during a background save.

maxmemory-policy is chosen deliberately and matches how this instance is used.

If a volatile-* policy is used, the keys expected to be evictable actually carry TTLs.

Every cache key is written with a TTL, and TTLs include jitter to avoid synchronised expiry.

Lazy freeing (lazyfree-lazy-eviction, lazyfree-lazy-expire, lazyfree-lazy-server-del) is enabled.

A big-key scan has been run and no single key is large enough to block the server when read or deleted.