LLM Apps in Production (RAG + Vector DB + Caching) · 课时

使用 Redis/Memcached 实现分布式缓存

使用 Redis 或 Memcached 等技术，为大规模 LLM 应用实现和管理分布式缓存。

第 1 / 4 课11 个步骤

使用 Redis/Memcached 实现分布式缓存 是 CoddyKit 上的免费 LLM Apps in Production (RAG + Vector DB + Caching) 课时。这是第 1 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 LLM Apps in Production (RAG + Vector DB + Caching) 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 LLM Apps in Production (RAG + Vector DB + Caching) 课程共包含 4 节课。

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

Distributed Caching: Why

When building high-scale LLM applications, you'll face challenges like high latency and increased API costs. Caching helps, but what happens when your app grows beyond a single server?

Distributed caching spreads your cache across multiple servers. This allows many application instances to share the same cached data, improving performance and consistency.

Scaling LLM Apps

Imagine your LLM app running on several servers. If each server has its own "in-memory" cache, they won't share data. This means:

Duplicate work: Server A might re-generate an LLM response already cached by Server B.
Inconsistent data: If one server updates its cache, others won't know.
Limited capacity: Each server's memory is finite.

Distributed caches solve these by providing a shared, external store.

Meet Redis: Key-Value Store

Redis (Remote Dictionary Server) is an open-source, in-memory data structure store, used as a database, cache, and message broker.

It's super fast because it keeps data in RAM.
It supports various data structures like strings, hashes, lists, sets, and more.
It's highly versatile and widely used for caching in distributed systems.

Redis: Setting & Getting Data

At its core, Redis works like a dictionary or hash map. You store data using a key and retrieve it using the same key.

For LLM apps, you might use a unique identifier (like a hashed prompt) as the key and the LLM's generated response as the value. Redis handles the storage and retrieval across your distributed setup.

Caching LLM Responses with Redis

Let's see how to use the redis-py library to connect to a Redis server and cache a simulated LLM response. This example assumes Redis is running locally.

import redis
import hashlib

# Connect to Redis (default host/port)
r = redis.Redis(host='localhost', port=6379, db=0)

def get_llm_response(prompt):
    # Simulate an LLM call
    print(f"Simulating LLM call for: '{prompt}'")
    return f"LLM response for '{prompt}'"

def get_cached_or_generate(prompt):
    # Create a simple cache key from the prompt
    cache_key = "llm_response:" + hashlib.md5(prompt.encode('utf-8')).hexdigest()

    # Try to get from cache
    cached_response = r.get(cache_key)

    if cached_response:
        print("Cache hit!")
        return cached_response.decode('utf-8')
    else:
        print("Cache miss. Generating response...")
        response = get_llm_response(prompt)
        # Store in cache with a 60-second expiry (TTL)
        r.setex(cache_key, 60, response)
        return response

if __name__ == "__main__":
    prompt1 = "Explain distributed caching in one sentence."
    prompt2 = "What is the capital of France?"

    print("--- First call for prompt1 ---")
    print(get_cached_or_generate(prompt1))

    print("\n--- Second call for prompt1 (should be cached) ---")
    print(get_cached_or_generate(prompt1))

    print("\n--- First call for prompt2 ---")
    print(get_cached_or_generate(prompt2))

    # Clean up (optional) - uncomment if you want to clear after running
    # r.delete("llm_response:" + hashlib.md5(prompt1.encode('utf-8')).hexdigest())
    # r.delete("llm_response:" + hashlib.md5(prompt2.encode('utf-8')).hexdigest())

Introducing Memcached

Memcached is another popular, high-performance, distributed memory object caching system.

It's simpler than Redis, focusing purely on caching key-value pairs.
Often used for caching database query results, API responses, or rendered HTML fragments.
It's designed for horizontal scaling, allowing you to add more servers easily.

Redis vs. Memcached: Comparison

Both are great for distributed caching, but have differences:

Redis: More feature-rich (data structures, persistence, pub/sub). Good for diverse use cases beyond simple caching.
Memcached: Simpler, pure caching solution. Often more memory-efficient for very large, simple key-value datasets.

For LLM applications, Redis's versatility often makes it a preferred choice, especially for more complex caching needs or when other Redis features are desired.

Designing Effective Cache Keys

A good cache key is crucial. For LLM responses, you need a key that uniquely identifies the request.

Hash the prompt: Use a cryptographic hash (like MD5 or SHA256) of the full prompt string.
Include parameters: If your LLM call has temperature, model name, or other parameters, include them in the hash.
Namespace: Prefix keys (e.g., "llm_response:...") to organize your cache.

Basic Cache Expiration (TTL)

Cached data can become stale. To prevent this, distributed caches support Time-To-Live (TTL), which automatically expires data after a set period.

You saw r.setex(key, 60, value) in the code. This sets the key to expire in 60 seconds. Choose a TTL based on how frequently your underlying data changes or how critical data freshness is.

Quick Check: Distributed Caching

You're designing a high-scale RAG application. You need to cache LLM responses across multiple instances of your application. Each instance should be able to access the same cached data.

Which approach is best suited for this requirement?

在交互式课程中回答

Recap: Distributed Caching

We've explored how distributed caching is essential for scaling LLM applications, addressing the limitations of local in-memory caches.

Redis and Memcached are powerful tools for building shared, high-performance caches.
We learned how to use Redis for basic key-value storage and retrieve LLM responses.
Effective cache key design and using Time-To-Live (TTL) are crucial for managing cache freshness.

This approach significantly improves performance and reduces operational costs for your LLM deployments.

免费开始

用 AI 导师学习 LLM Apps in Production (RAG + Vector DB + Caching) — 免费

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

课程: 12
课程: 48

免费开始学习查看完整课程

常见问题解答

「使用 Redis/Memcached 实现分布式缓存」课时是免费的吗？

是的 — 「使用 Redis/Memcached 实现分布式缓存」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 LLM Apps in Production (RAG + Vector DB + Caching) 课程的其余内容，请升级到 CoddyKit PRO。 LLM Apps in Production (RAG + Vector DB + Caching) 课程共包含 4 节课。

「使用 Redis/Memcached 实现分布式缓存」这节课中我会学到什么？

使用 Redis 或 Memcached 等技术，为大规模 LLM 应用实现和管理分布式缓存。你通过在浏览器中直接运行的动手代码来练习 LLM Apps in Production (RAG + Vector DB + Caching)，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 LLM Apps in Production (RAG + Vector DB + Caching) 需要有经验吗？

无需任何先前经验。CoddyKit 上的 LLM Apps in Production (RAG + Vector DB + Caching) 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 1 节课，共 4 节。

「使用 Redis/Memcached 实现分布式缓存」课时需要多长时间？

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

我能在这节 LLM Apps in Production (RAG + Vector DB + Caching) 课中编写并运行代码吗？

能。每节 LLM Apps in Production (RAG + Vector DB + Caching) 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 LLM Apps in Production (RAG + Vector DB + Caching)