Researchers introduced FluidPD, a P/D-disaggregated LLM serving system that provides SLO-aware in-place elasticity, improving SLO attainment by up to 94.6 percentage points over static SGLang on production Azure trace workloads.

1 min read

FluidPD: In-Place Elasticity for SLO-Aware Prefill-Decode Disaggregated LLM Serving

What's new in FluidPD?

FAQ

What is FluidPD?

FluidPD is a P/D-disaggregated LLM serving system that provides SLO-aware in-place elasticity through two complementary mechanisms: FluidToken and FluidRole.

How does FluidPD differ from traditional autoscaling?

Traditional autoscaling reacts slowly, requires spare GPUs, and does not directly address short-timescale phase imbalance. FluidPD handles both transient and sustained imbalance in place without adding workers.

What is the difference between FluidToken and FluidRole?

FluidToken handles transient imbalance by offloading a bounded portion of prefill computation to decode workers when decode-side slack is available. FluidRole handles sustained imbalance by reassigning running workers between prefill and decode roles in place, avoiding model reload and engine restart.

Should MENA infrastructure teams adopt this now?

The published results are positive on production Azure traces, but this remains arXiv research. Infrastructure teams can evaluate the concept in test environments while awaiting independent verification before production adoption.

Source: arXiv cs.AI

AI-assisted summary of the source above. High-confidence stories publish automatically; others wait for review. Facts that are not in the source are not added.