Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Story

vLLM adds push-based KV transfer for disaggregated inference

AI summary

A vLLM blog post introduces a push-based NIXL connector for prefill-decode disaggregated inference that has the decode instance register its destination blocks in advance and starts the transfer from a background thread, moving post-prefill coordination and setup off the time-to-first-token critical path. In the authors' benchmark using Qwen3-32B on a 1P1D deployment of Amazon EC2 P5en instances connected by AWS EFA, push mode delivered up to 3x better TTFT and up to 30% better time-per-output-token than the default pull-based mode, with results depending on workload and configuration. At 8 QPS and 16k input, TTFT was about 540 ms in push mode versus about 1,744 ms in pull mode. The feature was built and validated on AWS Trainium clusters with EFA and contributed to vLLM as an accelerator-agnostic capability.

In-depth insight

KV transfer sits on the critical path of prefill-decode disaggregation, so moving transfer coordination off that path can improve first-token and per-token latency for long-context, high-request-rate serving.

vLLM is an open-source inference and serving engine for large language models (LLMs). LLM inference has two distinct phases: prefill, which processes the input prompt and builds the key-value (KV) cache, and decode, which uses that cache to generate output one token at a time. These phases have different compute, memory, and scaling characteristics. Prefill-decode (P-D) disaggregation runs them on separate engine instances, allowing each phase to scale and be optimized independently. This can improve resource utilization, throughput, and latency under load. However, it also requires transferring the KV cache from the prefill instance to the decode instance before token generation can begin, making efficient KV transfer critical to time-to-first-token (TTFT).

One of the ways vLLM performs this transfer is through the NVIDIA Inference Xfer Library (NIXL) connector, which moves KV blocks over RDMA-capable interconnects such as AWS Elastic Fabric Adapter (AWS EFA, the low latency RDMA network used across servers in AWS). On supported instance types, AWS EFA supports GPUDirect RDMA and Neuron Direct RDMA, enabling NIXL to transfer KV blocks directly between GPU or Trainium device memory without staging through host memory. The default mode for NIXL connector is pull-based: After the prefill instance finishes computing the prompt KV cache, the router relays the source metadata, including the prefill block IDs, to the decode instance. The decode instance then allocates destination blocks, prepares the NIXL transfer, and initiates NIXL READ to pull the KV blocks from the prefill instance. Because these coordination and setup steps occur sequentially after prefill and before decoding can begin, they extend the TTFT critical path, as shown in the following timeline.

#vLLM#NVIDIA NIXL#AWS EFA#Amazon EC2 P5en#Qwen3-32B#AWS Trainium

Original · 12 min readRead the original
Group chat

No comments yet. Start the conversation.