[KongchangAI]
ConceptPrefill-Decode disaggregation / 预填充解码分离

Prefill-Decode Disaggregation

An architectural strategy in LLM inference systems that deploys the prefill stage and the decode stage on separate resources. By independently scaling compute for each stage, this approach optimizes overall inference throughput and latency.

Timeline (last 90 days)

Oct 29

Common optimization strategies for high-throughput prefill include chunked prefill, prefix cache reuse, and PD disaggregation (decoupled deployment of prefill/decode).

Unverified50%
Oct 21

DeepSeek adopts a PD-separated architecture, deploying the Pre-fill stage and the Decode stage on different machines: an 8-card server for reading the question and a 64-to-128-card supernode for writing the answer.

Unverified50%
Oct 20

Distributed inference parallelism strategies include tensor parallelism (TP), pipeline parallelism (PP), expert parallelism (EP), and PD disaggregation.

Unverified50%
Oct 19

Chunked prefill alleviates blocking by interleaving prefill slices with decode, but prefill and decode still share the same HBM bandwidth and SMs, so resource contention cannot be fundamentally eliminated.

Unverified50%
Oct 19

In a toy simulation with a 1B-class model and 16K to 64K token prompts, PD disaggregation reduced p99 inter-token latency from 5.0ms to 1.0ms and the worst-case stall from 931ms to 1ms.

Unverified50%
Oct 19

If a team is already deploying vLLM with PD disaggregation, bidirectional KV transfer is a natural upgrade; if it is still deploying on a single node, it needs to consider the network dependency introduced by cross-node transfer, because high-speed interconnects like EFA are not available in all environments.

Unverified50%
Oct 4

PD disaggregation deploys the compute-intensive Prefill stage and the memory-bandwidth-intensive Decode stage of inference on separate instances for independent scaling and optimization

Unverified50%
Sep 24

PD separation breaks data locality, as the KV cache generated by prefill nodes needs to be transferred to decode nodes over the network, with bandwidth consumption and latency increasing as input sequence length grows

Unverified50%
Sep 24

OpenAI has not adopted a prefill-decode separated PD architecture on its in-house chips

Unverified50%
Sep 23

Prefill-Decode (PD) disaggregation requires transferring KV Cache from the Prefill instance to the Decode instance; a CX7 NIC at full 400 Gbps IB delivers approximately 50 GB/s, and transferring 40 GB of KV Cache takes 0.8 seconds.

Unverified50%

1 more timeline events

All Facts (11)

Unverified

Common optimization strategies for high-throughput prefill include chunked prefill, prefix cache reuse, and PD disaggregation (decoupled deployment of prefill/decode).

50%
Unverified

DeepSeek adopts a PD-separated architecture, deploying the Pre-fill stage and the Decode stage on different machines: an 8-card server for reading the question and a 64-to-128-card supernode for writing the answer.

50%
Unverified

Distributed inference parallelism strategies include tensor parallelism (TP), pipeline parallelism (PP), expert parallelism (EP), and PD disaggregation.

50%
Unverified

Chunked prefill alleviates blocking by interleaving prefill slices with decode, but prefill and decode still share the same HBM bandwidth and SMs, so resource contention cannot be fundamentally eliminated.

50%
Unverified

In a toy simulation with a 1B-class model and 16K to 64K token prompts, PD disaggregation reduced p99 inter-token latency from 5.0ms to 1.0ms and the worst-case stall from 931ms to 1ms.

50%
Unverified

If a team is already deploying vLLM with PD disaggregation, bidirectional KV transfer is a natural upgrade; if it is still deploying on a single node, it needs to consider the network dependency introduced by cross-node transfer, because high-speed interconnects like EFA are not available in all environments.

50%
Unverified

PD disaggregation deploys the compute-intensive Prefill stage and the memory-bandwidth-intensive Decode stage of inference on separate instances for independent scaling and optimization

50%
Unverified

PD separation breaks data locality, as the KV cache generated by prefill nodes needs to be transferred to decode nodes over the network, with bandwidth consumption and latency increasing as input sequence length grows

50%
Unverified

OpenAI has not adopted a prefill-decode separated PD architecture on its in-house chips

50%
Unverified

Prefill-Decode (PD) disaggregation requires transferring KV Cache from the Prefill instance to the Decode instance; a CX7 NIC at full 400 Gbps IB delivers approximately 50 GB/s, and transferring 40 GB of KV Cache takes 0.8 seconds.

50%
Unverified

Splitwise, DistServe, and Mooncake are all representative implementations of prefill-decode (PD) disaggregation.

50%

Source Articles