Skip to main content

2 posts tagged with "Disaggregation"

Disaggregated inference serving

View All Tags

Topology as an End-to-End Contract: P/D Disaggregated Inference in llm-d on GKE

ยท 37 min read
Xia Hua
Xia Hua
Software Engineer, Google

Production lessons from RDMA-backed Prefill/Decode serving across H200, B200, GB200, and GB300 on GKE

The Contract, and What Upholding It Is Worthโ€‹

This post is the technical summary of a four-platform bring-up story, and the story converges on one systems lesson: topology is not only a transport optimization; it is an end-to-end contract spanning allocator, kernel, NIC, transport, engine, and router. Concretely, the contract imposes four obligations: topology must be discovered by the platform, preserved through resource allocation, verified at runtime, and consumed by the router โ€” the allocation, verification, and routing sections that follow are one production stack's evidence for each.

Disaggregating LLM serving into separate Prefill and Decode (P/D) phases changes what kind of system you are running: the KV state that decode needs often has to leave the accelerator domain that produced it. The failures we hit while bringing up llm-d on GKE shared one shape: topology information the hardware knew was dropped somewhere between the allocator, the runtime, and the router, and the loss surfaced far from its origin. The bring-up itself was a first: llm-d's P/D guide had no GKE RDMA recipe before this work introduced one on A3 Ultra, then carried the same allocation-and-transport contract through A4, A4X, and A4X Max (allocation).

Three results from our own environment frame what upholding the contract is worth:

  • Restoring the verified RDMA (Remote Direct Memory Access) path cut mean KV-transfer time by more than 93% versus the silent-fallback path it replaced.
  • On a separate H200 benchmark cluster (evaluation), 436 of 5,400 requests on an intentional TCP baseline (UCX's TCP path over the datacenter network, DCN) timed out, while the RDMA configuration on the same cluster completed all 5,400.
  • Mean time-to-first-token (TTFT) descended a ladder on one cluster: 2.15 s under unconstrained placement, 1.157 s with deterministic DRA allocation and the RDMA channel verified end-to-end, and 0.33 s with topology-scored P/D pairing on top (an experimental router prototype โ€” routing) โ€” a further 3.5x mean improvement. (All means; percentiles and provenance in evaluation.)

An earlier llm-d post, Networking for Distributed Inference in llm-d, covered the transport stack itself โ€” NIXL (NVIDIA Inference Xfer Library), UCX (Unified Communication X), and backend performance; this post covers how topology survives from resource allocation all the way into routing.

Scaling Vision-Heavy Kimi-VL with Heterogeneous E/PD on llm-d and SGLang

ยท 7 min read
Xiaojun(Robin) Zhang
Xiaojun(Robin) Zhang
AI Software Solutions Engineer, Intel
Weifeng(Matrix) Yao
Weifeng(Matrix) Yao
AI Principal Engineer, Intel
Fan Zhao
Fan Zhao
Senior Engineering Director, Intel
Yuan Wu
Yuan Wu
AI Frameworks Engineer, Intel
Jianan Gu
Jianan Gu
AI Frameworks Engineer, Intel
Carlos Costa
Distinguished Engineer, IBM
Alex Nails
Alex Nails
Member of Technical Staff, RadixArk

Vision-language model (VLM) inference involves several stages: vision encoding, language model prefill, and language model decode. Each stage has different compute and memory characteristics, making heterogeneous disaggregation a natural fit. This gives us the flexibility to place different stages to different accelerator resources based on their compute and memory characteristics.

In this post, we evaluate a vision-heavy Kimi-VL serving workload on llm-d and SGLang. We place vision encoding stage in 4 Intel Arc Pro B60 (Intel B60) GPUs while keeping prefill and decode stage on 1 NVIDIA H200 GPU. Compared with the collocated baseline, the measured heterogeneous E/PD configuration achieved 2.4x-2.8x higher throughput and reduced mean Time To First Token (TTFT) by roughly 69%-80% under load.