Redis Caching & Messaging (Pub/Sub, Streams) · 课时

缓存淘汰与过期

掌握管理缓存大小、设置过期时间(TTL)以及处理缓存失效的技术

第 3 / 4 课11 个步骤

缓存淘汰与过期 是 CoddyKit 上的免费 Redis Caching & Messaging (Pub/Sub, Streams) 课时。 这是第 3 节课,共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Redis Caching & Messaging (Pub/Sub, Streams) 学习路径的一部分,你的进度在网页和 CoddyKit 应用中同步。 Redis Caching & Messaging (Pub/Sub, Streams) 课程共包含 4 节课。

本课时的部分内容尚未翻译,以英文显示。

Why Cache Expiration Matters

Caching is great for speed, but cached data can become stale, meaning it no longer reflects the true source of information. Also, caches have limited memory.

This lesson explores how to manage these issues using expiration and eviction techniques in Redis.

Introducing Time To Live (TTL)

Time To Live (TTL) defines how long a cached item remains valid. Once its TTL expires, Redis automatically removes the key.

  • Prevents stale data from being served indefinitely.
  • Frees up memory for newer, more relevant data.

Setting TTL with EXPIRE

The EXPIRE command sets an expiration time, in seconds, on an existing key. After the set time, the key will be automatically deleted.

Try setting a key and then giving it a 10-second expiration:

SET myapp:user:1 "John Doe"
EXPIRE myapp:user:1 10
TTL myapp:user:1

SETEX: Set and Expire Together

Instead of two commands (SET then EXPIRE), you can use SETEX to set a key's value and its expiration time atomically (in one go).

This is generally preferred for new keys as it's more efficient.

SETEX myapp:product:5 20 "LaptopX"
TTL myapp:product:5

Checking TTL & Persistence

You can check a key's remaining TTL with the TTL command. It returns the remaining seconds, or -2 if the key doesn't exist, -1 if it exists but has no expiration.

The PERSIST command removes the expiration from a key, making it permanent again.

SET temp:token "abc123"
EXPIRE temp:token 5
TTL temp:token
PERSIST temp:token
TTL temp:token

Millisecond Precision with PEXPIRE

For more precise control, PEXPIRE and PSETEX work just like their second-based counterparts, but accept expiration times in milliseconds.

This can be useful for very short-lived caches or specific timing requirements.

SET mskey:data "important info"
PEXPIRE mskey:data 5000
PTTL mskey:data

Automatic Eviction Policies

What happens when your Redis cache runs out of memory? Redis can be configured to automatically evict (remove) keys to free up space.

This behavior is controlled by the maxmemory setting and an eviction policy.

Common Eviction Policies

Redis offers several eviction policies configured via maxmemory-policy:

  • noeviction: Returns errors on write operations when memory limit is reached.
  • allkeys-lru: Evicts least recently used (LRU) keys from all keys.
  • volatile-lru: Evicts LRU keys *only* from those with an explicit TTL set.
  • allkeys-random: Evicts random keys from all keys.

Manual Cache Invalidation

Sometimes, data changes unexpectedly, or you need to ensure a cache entry is immediately removed. In such cases, you can manually invalidate a key.

The DEL command removes one or more specified keys from Redis immediately.

SET cache:user:1 "user_data_old"
GET cache:user:1
DEL cache:user:1
GET cache:user:1

Quick Check: Expiration

You have a Redis key named session:user:123. You want it to expire in exactly 30 minutes from now. Which command would achieve this?

Recap: Eviction & Expiration

In this lesson, you mastered key techniques for managing cached data in Redis:

  • Using EXPIRE, SETEX, and PEXPIRE to set time-based expirations.
  • Understanding TTL and PERSIST to manage key lifetimes.
  • Learning about automatic eviction policies to handle memory limits.
  • Implementing manual cache invalidation with DEL for immediate updates.

These skills are crucial for maintaining fresh data and efficient memory usage in your Redis cache!

免费开始

用 AI 导师学习 Redis Caching & Messaging (Pub/Sub, Streams) — 免费

在浏览器中编写并运行真实代码,获得全天候 AI 导师的即时帮助,并在网页或应用中继续学习。

课程
12
课程
48

常见问题解答

「缓存淘汰与过期」课时是免费的吗?

是的 — 「缓存淘汰与过期」的完整文本可在网页上免费阅读。要进行交互式练习(内置代码编辑器和全天候 AI 导师)并解锁 Redis Caching & Messaging (Pub/Sub, Streams) 课程的其余内容,请升级到 CoddyKit PRO。 Redis Caching & Messaging (Pub/Sub, Streams) 课程共包含 4 节课。

「缓存淘汰与过期」这节课中我会学到什么?

掌握管理缓存大小、设置过期时间(TTL)以及处理缓存失效的技术 你通过在浏览器中直接运行的动手代码来练习 Redis Caching & Messaging (Pub/Sub, Streams),全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Redis Caching & Messaging (Pub/Sub, Streams) 需要有经验吗?

无需任何先前经验。CoddyKit 上的 Redis Caching & Messaging (Pub/Sub, Streams) 课程适合初学者到高级学习者,你可以从这里开始或从头开始,按照自己的节奏学习。 这是第 3 节课,共 4 节。

「缓存淘汰与过期」课时需要多长时间?

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动,所以你能稳步进步,并在网页和应用中从离开的地方继续。

我能在这节 Redis Caching & Messaging (Pub/Sub, Streams) 课中编写并运行代码吗?

能。每节 Redis Caching & Messaging (Pub/Sub, Streams) 课都包含内置代码编辑器,你可以在浏览器中直接编写并运行真实代码,并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. 为什么需要缓存?缓存简介
  2. 实现基本缓存模式
  3. 缓存淘汰与过期
  4. 防止缓存击穿与惊群
← 返回 Redis Caching & Messaging (Pub/Sub, Streams)