lmcache-mp

Run LMCache MP to share KV caches among vLLM pods in Kubernetes clusters.

5|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/air-gapped/skills --skill lmcache-mp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lmcache-mp
Source: https://github.com/air-gapped/skills/tree/main/.claude/skills/lmcache-mp
Command: npx skills add https://github.com/air-gapped/skills --skill lmcache-mp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

LMCache multiprocess (MP) mode runs the KV-cache server in its own process so multiple vLLM pods on a node can share a centralized cache with independent CPU/memory budgets and a ZMQ-based transport, enabling scalable inference at scale.

Core Features & Use Cases

  • Separate LMCache server per node that serves multiple vLLM pods on the same node, reducing GPU contention and improving cache hit rates for multi-pod deployments.
  • Kubernetes-friendly deployment pattern: a DaemonSet for LMCache and a Deployment for vLLM pods, using L1/L2 storage cascades (nixl_store, nixl_store_dynamic, fs, mooncake_store, s3) as configured.
  • Production-ready references: operator-based reconciliation and example manifests, plus detailed deployment and troubleshooting guidance.

Quick Start

Start a LMCache MP DaemonSet on your cluster and configure vLLM to connect to the LMCache MP port.

Frequently Asked Questions about lmcache-mp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I share KV caches among multiple vLLM pods in Kubernetes?

Sharing KV caches across vLLM pods requires a separate LMCache multiprocess server per node deployed as a DaemonSet, serving all pods via ZMQ transport.

What is the best way to offload vLLM KV cache to reduce GPU memory contention in production?

Offloading vLLM KV cache to a dedicated LMCache multiprocess server reduces GPU contention by isolating cache management in its own process with independent CPU and memory budgets separate from the inference pods.

How do I configure L1 and L2 cache storage for vLLM pods on Kubernetes?

Configure L1 and L2 cache storage cascades for vLLM pods by selecting adapters like nixl_store, fs, mooncake_store, or s3 within your Kubernetes Deployment manifests.

Do I need specific network and IPC settings to run LMCache multiprocess mode?

Yes, LMCache multiprocess mode requires hostNetwork configuration and /dev/shm sharing for inter-process communication between the DaemonSet and vLLM pods.

Can I use LMCache MP with any version of vLLM?

No, LMCache MP requires aligned vLLM and LMCache versions plus correct startup flags to ensure proper connectivity between the cache server and inference pods.

Why does vLLM fail to connect to the LMCache MP server?

Connection failures between vLLM and LMCache MP typically stem from misaligned versions, incorrect startup flags, or missing hostNetwork and /dev/shm configurations for IPC.