vllm-caching

Coordinate vLLM KV caching across native offload, LMCache, Nixl, and Mooncake backends.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Tiered KV caching for vLLM workloads enables production-grade long-context inference by offloading KV data to CPU DRAM, NVMe, or disaggregated backends, reducing re-fetches and latency.

Core Features & Use Cases

  • Supports Native CPU offload, LMCache DRAM+NVMe, NixlConnector for disaggregated prefill, MooncakeConnector for RDMA, and MultiConnector to compose backends.
  • Provides sizing guidance and version-gated recommendations to optimize throughput and hit rates for long-context prompts.
  • Use case: operate a multi-GPU vLLM service with high-context sessions and daily re-use of prompts across requests.

Quick Start

Configure a vLLM deployment to enable tiered KV caching and verify a small benchmark.

Frequently Asked Questions about vllm-caching

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

FAQPage Schema
How do I configure vLLM KV caching for long-context inference?▼

Configure vLLM KV caching by selecting native CPU offload, LMCache, or disaggregated backends like Mooncake. This offloads KV data to CPU DRAM or NVMe, reducing re-fetches and optimizing latency for long-context inference.

What is the best way to offload KV cache in a multi-GPU vLLM deployment?▼

The best way to offload KV cache in multi-GPU vLLM deployments is using LMCache for DRAM+NVMe or MooncakeConnector for RDMA. MultiConnector can compose these backends to optimize throughput and hit rates.

Does vLLM support disaggregated prefill with RDMA backends?▼

vLLM supports disaggregated prefill with RDMA backends via the MooncakeConnector. NixlConnector also enables disaggregated prefill scenarios, coordinating KV cache transfers across H100 and H200 GPU clusters.

Can I use LMCache and native CPU offload together in vLLM?▼

You can compose LMCache DRAM+NVMe with native CPU offload using the MultiConnector. This tiered KV caching approach allows vLLM to layer backends, balancing latency and hit rates for long-context prompts.

How do I size vLLM KV cache to maximize hit rates for long-context prompts?▼

Size vLLM KV cache by applying the sizing math and version-gated recommendations provided for tiered offload. Properly sizing KV cache directly impacts latency and hit rates for daily re-use of long-context prompts.

When should I not use tiered KV offload for vLLM workloads?▼

Tiered KV offload for vLLM may not suit workloads lacking prompt re-use across requests or single-GPU setups without disaggregated prefill. Without high-context sessions, offloading KV data yields minimal latency benefits.