LLM Inference Efficiency: Phase, Layer, and Time Splitting Strategies Driving Cost Compression · history
Version 2
2026-07-03 08:31 UTC · 101 items
What
LLM inference is being subdivided through three successive hardware-level splits: prefill-decode disaggregation (routing compute-bound prefill and bandwidth-bound decode to separate hardware pools), attention-FFN disaggregation (routing attention and feed-forward layers to hardware matched to each operation's memory profile), and time-based interleaving. [1][2] Prefill-decode disaggregation is production-mature, with Anyscale reporting 67% cost savings on AMD MI325X [5] and llm-d claiming 70% higher throughput. [6] Attention-FFN disaggregation (AFD) has moved from theoretical proposal to active research, with multiple named systems — AiDE [10], CMU operator-level disaggregated serving [11] — and a vLLM production RFC now tracking implementation. [14] A practical constraint has emerged: at least one practitioner argues disaggregation only pays at fleet scale, where traffic is sufficient to keep split prefill and decode pools both continuously utilized. [7]
Why it matters
Each split recovers compute that would otherwise sit idle, lowering cost per token without sacrificing model quality. The layer-level AFD split is now close enough to production that its feasibility at typical deployment scales — not just research benchmarks — will determine whether it joins PD disaggregation as a standard serving technique or remains confined to large-fleet operators.
Open questions
Does attention-FFN disaggregation deliver its theoretical gains in production, or does inter-node KV transfer overhead neutralize the benefit outside of large fleets? [13][7]
Will prefill-decode aggregation and disaggregation converge into a unified architecture, as a recent arXiv paper proposes, or will the binary architectural choice persist? [20]
Can JetSpec's 9.64x benchmark speedup translate at similar ratios once integrated into vLLM and SGLang in production workloads? [16][17]
Does the demand-expansion thesis hold as per-token costs keep falling, or will enterprise inference spending plateau regardless of unit economics? [1][21]
Narrative
LLM inference has been progressively subdivided by hardware function, with each subdivision designed to eliminate idle compute that results from mixing workloads with incompatible resource profiles. SemiAnalysis laid out a three-part framework as the organizing theme of MLSys 2026: a phase split routes prefill (compute-bound) and decode (memory-bandwidth-bound) to separate hardware pools suited to each; a layer split routes attention layers (memory-hungry, favoring HBM-rich GPUs) and feed-forward layers (compute-hungry, favoring SRAM-based silicon) to different chip types; and time-based interleaving alternates workload slices across a shared chip set to fill gaps that would otherwise sit idle. [1][2] The common logic across all three, per SemiAnalysis, is finding idle compute and filling it — each step lowering cost per token and, the argument goes, growing total demand rather than compressing margins.
Prefill-decode (PD) disaggregation is the most production-mature technique. The core problem it addresses is that prefill and decode compete for the same GPU when co-located: prefill requires high compute throughput while decode is bottlenecked by memory bandwidth, so a unified deployment forces a sub-optimal compromise for both. [3][4] Routing each to a dedicated hardware pool eliminates that compromise at the cost of transferring the KV cache between pools — a real overhead practitioners treat as manageable. [4] Anyscale reported 67% cost savings with Ray and vLLM on AMD MI325X [5]; the Kubernetes-native llm-d stack claims up to 70% higher tokens per second through the same approach, adding intelligent routing and autoscaling on top of standard serving infrastructure. [6] However, at least one practitioner (Rompel) argues that disaggregation only pays at fleet scale, where enough traffic keeps split prefill and decode pools both continuously utilized; KV-aware routing at lower traffic volumes does not justify the infrastructure overhead. [7] UCSD's Hao AI Lab, whose DistServe paper established the theoretical basis for PD disaggregation around maximizing goodput (tokens delivered within latency SLA) rather than raw throughput, tracked adoption from initial proposal in 2024 through substantial production uptake by late 2025. [8][9]
Attention-FFN disaggregation (AFD) — the layer-level split in the three-cut framework — has moved from theoretical proposal to active research and early production planning. Multiple systems have been published: AiDE (Attention-FFN Disaggregated Execution) targets cost-effective serving [10]; a CMU PhD blog covers operator-level disaggregated serving [11]; researchers have derived theoretically optimal attention/FFN ratios for disaggregated configurations [12]; and a design-space exploration paper examines how far disaggregation can be extended beyond the phase level. [13] On the open-source side, a vLLM RFC tracks attention-FFN disaggregation for mixture-of-experts models specifically, where the attention/FFN ratio is already architecturally distinct. [14] Glenn Klockwood's technical notes document the AFD concept and implementation considerations. [15] The layer split targets a different inefficiency than the phase split: in dense models and especially MoE architectures, attention and FFN layers have different compute-to-memory ratios, so routing them to hardware optimized for each avoids forcing both through a single GPU type that is well-matched to only one.
Three further efficiency angles run parallel to the disaggregation story. JetSpec, from Hao AI Lab, applies causal parallel tree speculative decoding to reach 9.64x speedup on MATH-500 and approximately 1,000 tokens per second on a single B200 GPU, with vLLM and SGLang production integration still forthcoming. [16][17] A paper on Grouped Query Experts finds that attention can be made sparse within grouped-query attention — each token using only 9 of 16 query heads — achieving 1.7–1.8x faster prefill for long-context inputs while matching baseline accuracy. [18] And a Meta paper on quantized reasoning models finds that aggressive quantization raises overthinking failures (second-guessing already-correct answers) by up to 52% across benchmarks, though a lightweight fix — a decoding penalty on 50 hesitation tokens — reduces reasoning chain length by 12–23% while maintaining accuracy. [19] These results collectively show that inference efficiency is being pursued at multiple levels simultaneously: hardware routing, speculative decoding, attention sparsification, and decode-time behavioral correction.
Timeline
- 2024-01-01: UCSD Hao AI Lab proposes DistServe, establishing PD disaggregation's theoretical basis around maximizing goodput rather than raw throughput. [8][9][30]
- 2025-12-01: Prefill-decode disaggregation moves from early research proposal to substantial production adoption. [30]
- 2026-06-16: Anyscale publishes benchmark showing 67% cost savings with Ray+vLLM PD disaggregation on AMD MI325X. [5]
- 2026-06-25: Industry commentary notes AI inference costs falling; developer shift toward price-competitive open-weight and Chinese models attributed to inference economics. [31][32]
- 2026-06-26: Red Hat publishes Part 1 of its distributed LLM inference series covering PD disaggregation, KV cache tiering, and EAGLE speculative decoding. [23][24]
- 2026-06-27: Grouped Query Experts paper: 1.7–1.8x faster prefill using only 9 of 16 query attention heads, matching baseline accuracy on long-context inputs. [18]
- 2026-06-28: Report of a Chinese AI lab achieving an inference milestone the industry expected to take years longer. [33]
- 2026-06-29: llm-d Kubernetes-native inference stack highlighted for 70% throughput gains via PD disaggregation with intelligent routing and autoscaling. [25][6]
- 2026-06-29: Practitioner thread (Prajjwal, nanoserve) explains the compute/bandwidth conflict in unified serving and the KV-cache transfer cost of disaggregation as a real but manageable trade-off. [3][4]
- 2026-06-30: Red Hat publishes Part 2 of its distributed inference series on advanced disaggregation topics. [22]
- 2026-06-30: SemiAnalysis amplifies JetSpec results: 9.64x speedup on MATH-500, 4.58x on open-ended chat, approximately 1,000 TPS on a single B200 GPU. [16]
- 2026-07-01: SemiAnalysis publishes three-cut framework (phase, layer, time splitting) as the central inference-efficiency narrative from MLSys 2026. [1][2]
- 2026-07-01: Meta paper finds aggressive quantization raises overthinking failures in reasoning models by up to 52%; a 50-token decoding penalty largely resolves it. [19]
- 2026-07-01: AMD Helios proposed as a native GPU disaggregation solution; AMD receives analyst upgrades to $1T–$1.14T market cap range on inference hardware positioning. [27][28]
- 2026-07-02: Practitioner (Rompel) argues disaggregation only pays at fleet scale, where traffic volume keeps split prefill and decode pools continuously utilized. [7]
- 2026-07-02: Multiple AFD papers now in evidence: AiDE, CMU operator-level disaggregated serving, theoretically optimal attention/FFN ratios, and a design-space exploration paper extending disaggregation beyond the phase level. [10][11][12][13][15][14]
Perspectives
SemiAnalysis
Frames phase, layer, and time splitting as a unified progression recovering wasted hardware utilization; argues cheaper tokens grow total AI demand rather than compress revenue; treats MLSys 2026 as the point where this became the defining inference narrative.
Evolution: Consistent analytical and demand-bullish position across JetSpec amplification and the three-cut macro thread.
UCSD Hao AI Lab
Originators of both DistServe (PD disaggregation, optimizing goodput over raw throughput) and JetSpec (causal parallel tree speculative decoding); positions the two as complementary inference optimization strategies.
Evolution: Consistent research framing; JetSpec represents a newer line beyond disaggregation.
Anyscale (Robert Nishihara)
Production validation: 67% cost savings with Ray+vLLM PD disaggregation on AMD MI325X demonstrates disaggregation is deployable at scale on non-NVIDIA hardware.
Evolution: Consistent; single data point.
Red Hat
Enterprise infrastructure framing: treats disaggregation, KV cache tiering, and speculative decoding as production-ready techniques for enterprise customers rather than research-stage work.
Evolution: Consistent across both published parts of the series.
Prajjwal / nanoserve
Disaggregation solves a real compute/bandwidth conflict but introduces KV cache transfer overhead; practitioners must weigh the trade-off explicitly rather than treating disaggregation as a free optimization.
Evolution: Consistent; single entry.
Rompel (practitioner)
Disaggregation only pays at fleet scale: split prefill/decode plus KV-aware routing requires enough sustained traffic to keep both pools utilized; smaller deployments may not break even on the infrastructure cost.
Evolution: New voice this pass.
AFD research community (AiDE, CMU, academic papers)
Attention-FFN disaggregation is theoretically grounded and implementable; multiple systems show that routing attention and FFN layers to hardware matched to each operation's profile improves efficiency, with optimal ratios now derivable analytically.
Evolution: New consolidated voice; represents the layer-level split gaining concrete research backing.
Open-source ecosystem (llm-d, vLLM, Ray)
Kubernetes-native stacks like llm-d are productizing PD disaggregation with intelligent routing and autoscaling; vLLM's RFC for attention-FFN disaggregation signals that AFD is next in the production integration pipeline.
Evolution: Extended to include AFD RFC alongside existing PD disaggregation coverage.
Tensions
- Fleet-scale requirement vs. claimed savings: Rompel argues disaggregation only pays when traffic is sufficient to keep split pools utilized, while Anyscale and llm-d report 67–70% savings without specifying a minimum scale threshold. [7][5][6]
- Disaggregation vs. unified architecture: a recent arXiv paper argues prefill-decode aggregation and disaggregation should be unified rather than treated as a binary choice, while production deployments treat disaggregation as the clear efficiency winner. [20][5][6]
- Cost compression vs. demand expansion: SemiAnalysis argues falling per-token costs grow total AI demand; some market observers treat the same trend as deflationary pressure on AI revenue. [1][21][26]
- NVIDIA vs. AMD for disaggregated inference: Anyscale's 67% savings result is on AMD MI325X and AMD Helios is proposed as a native disaggregation solution, directly contesting NVIDIA's assumed inference hardware dominance. [5][27][28]
- Throughput vs. goodput as the right optimization target: DistServe's framing argues maximizing raw throughput ignores latency SLAs; the correct metric is goodput (tokens delivered within SLA), which changes how disaggregation trade-offs should be evaluated. [8][9][29]
Sources
- [1] Inference keeps getting carved up, and every cut makes intelligence cheaper. — SemiAnalysis Twitter (2026-07-01)
- [2] A quick map of the three cuts. — SemiAnalysis Twitter (2026-07-01)
- [3] Prefill and decode fight for the same GPU. Prefill is compute bound, decode is memory bandwidth bound. Run them in the s... — reactive:inference-cost-optimization (2026-06-29)
- [4] Disaggregation goes further: prefill on one GPU pool, decode on another, ship the KV cache between them. You pay a trans... — reactive:inference-cost-optimization (2026-06-29)
- [5] 67% Cost Savings with PD Disaggregation Using Ray and vLLM on AMD MI325X — reactive:inference-cost-optimization (2026-06-16)
- [6] @GithubProjects Prefill/decode disaggregation yielding up to 70% higher tokens/sec is massive for scaling large models w... — reactive:inference-cost-optimization (2026-06-29)
- [7] @hasantoxr Disaggregation only pays at fleet scale. Split prefill/decode + KV-aware routing needs enough traffic to keep... — reactive:inference-cost-optimization (2026-07-02)
- [8] [2401.09670] DistServe: Disaggregating Prefill and Decoding for Goodput-optimized Large Language Model Serving — reactive:mlsys-2026-inference-systems
- [9] Throughput is Not All You Need: Maximizing Goodput in LLM Serving using Prefill-Decode Disaggregation | Hao AI Lab @ UCSD — reactive:inference-cost-optimization
- [10] AiDE: Attention-FFN Disaggregated Execution for Cost-Effective ... — reactive:inference-cost-optimization
- [11] CMU CSD PhD Blog - Operator-Level Disaggregated Serving for Efficient LLM Inference — reactive:inference-cost-optimization
- [12] Theoretically Optimal Attention/FFN Ratios in Disaggregated LLM ... — reactive:inference-cost-optimization
- [13] How Far Can Disaggregation Go? A Design-Space Exploration of ... — reactive:inference-cost-optimization
- [14] [RFC]: ATTN-FFN Disaggregation for MoE Models #22799 - GitHub — reactive:mlsys-2026-inference-systems
- [15] Attention-FFN disaggregation — reactive:mlsys-2026-inference-systems
- [16] Parallel draft tree, tree-causal verification — SemiAnalysis Twitter (2026-06-30)
- [17] GitHub - hao-ai-lab/JetSpec: JetSpec: Breaking the Scaling Ceiling of Speculative Decoding with Causal Parallel Tree Drafting · GitHub — reactive:inference-cost-optimization
- [18] This paper makes long-context attention cheaper and faster by letting each token use only the query heads it needs. — Rohan Paul Twitter (2026-06-27)
- [19] Paper from Meta shows Quantized reasoning models often lose because they keep doubting a correct answer instead of finis… — Rohan Paul Twitter (2026-07-01)
- [20] Prefill-Decode Aggregation or Disaggregation? Unifying Both ... - arXiv — reactive:inference-cost-optimization
- [21] AI quarterly revenue surpasses depreciation costs for the first time—has the trillion-dollar bet on computing power ente... — reactive:inference-cost-optimization (2026-06-26)
- [22] Part 2 of our 𝗗𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗲𝗱 𝗔𝗜 𝗜𝗻𝗳𝗲𝗿𝗲𝗻𝗰𝗲 series is now live on Red Hat Developer: 𝘖𝘱𝘵𝘪𝘮𝘪𝘻𝘪𝘯𝘨 𝘋𝘪𝘴𝘵𝘳𝘪𝘣𝘶𝘵𝘦𝘥 𝘈𝘐 𝘐𝘯𝘧𝘦𝘳𝘦𝘯𝘤𝘦: 𝘈𝘥𝘷... — reactive:inference-cost-optimization (2026-06-30)
- [23] Red Hat posted a technical article on distributed LLM inference: prefill/decode disaggregation, KV cache tiering, EAGLE ... — reactive:inference-cost-optimization (2026-06-27)
- [24] Scale your distributed #AI inference from a single vLLM instance to a multi-tenant grid. Explore prefill-decode disaggre... — reactive:inference-cost-optimization (2026-06-26)
- [25] llm-d is a Kubernetes-native inference serving stack that adds intelligent routing, KV-cache management, and autoscaling... — reactive:inference-cost-optimization (2026-06-29)
- [26] OpenAI and Anthropic love to compare AI to electricity. 'AI will be like a utility,' they say. 'Infrastructure for the n... — reactive:inference-cost-optimization (2026-06-30)
- [27] @MilkRoadAI $AMD will solve this issue with Helios by providing for native GPU disaggregation. — reactive:inference-cost-optimization (2026-07-01)
- [28] $AMD is now re-rated to $1T - $1.14T market cap from different analysts/researched firms🧵 — reactive:inference-cost-optimization (2026-06-29)
- [29] Compute-bound and memory-bandwidth-bound are not the same problem. Treating them like one is costing you throughput. — reactive:inference-cost-optimization (2026-06-30)
- [30] UC San Diego Hao AI Labのブログ非常に分かりやすくDistServeのPrefill Decode Disaggregationの有用性について解説している上に、DistServeを提案した2024年から2025年末ま... — reactive:inference-cost-optimization (2026-06-27)
- [31] The cost of running an AI model dropped again this week, and the trend is the whole story. — reactive:inference-cost-optimization (2026-06-25)
- [32] The shift toward Chinese/open-weight models was already happening because developers follow price, latency, availability... — reactive:gpt-56-launch-government-access (2026-06-26)
- [33] A Chinese AI lab just pulled off something the AI industry thought would take years. — reactive:inference-cost-optimization (2026-06-28)