IX2-0461

① SA Source

Context Before

Source: DistServe

Disaggregation also enables independent scaling and optimization of each phase. With separate nodes, each phase can be tuned independently: different parallelism strategies, different batch sizes, and different memory allocation ratios. The ratio of prefill to decode nodes can also be matched to the workload’s input-output length ratio. For instance, prefill-dominated workloads (long input, short output e.g., summarization, RAG, agentic coding with large context windows) allocate more prefill instances. Decode-dominated workloads (short input, long output e.g., chain-of-thought reasoning, long-form generation) allocate more decode instances. Workloads with high cache hit rates also tend toward more decode, since reused KV cache entries from shared system prompts or multi-turn conversation history skip prefill entirely.

Evidence

After prefill completes, the full KV cache for that request must be transmitted from the prefill node to the decode node before the first decode token can be generated

Context After

image

Source: Github

② Atomic Claim

prefill 完成後,該 request 的完整 KV cache 必須先從 prefill node 傳到 decode node,之後才能產生第一個 decode token。

  • Epistemic Mode: ASSERTED
  • Mapping Status: COMPLETE

③ Semantic Frame

{
  "attribute": "COUNT",
  "context_nodes": [
    {
      "id": "04_knowledge_base/KV cache",
      "label": "KV cache"
    },
    {
      "id": "04_knowledge_base/Decode",
      "label": "decode"
    }
  ],
  "entity": {
    "id": "04_knowledge_base/Prefill",
    "label": "prefill"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [],
    "value_text": "prefill 完成後,該 request 的完整 KV cache 必須先從 prefill node 傳到 decode node,之後才能產生第一個 decode token。"
  }
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
entityprefillPrefill
context_0KV cache04_knowledge_base/KV cache
context_1decodeDecode

⑤ Human Review

請在 Properties 逐項確認:

  • 原文 → Atomic Claim 是否忠實
  • Atomic Claim → Semantic Frame 是否忠實
  • Canonical Entity mapping 是否正確
  • Epistemic mode 是否保留原文語氣
  • 最後選擇 review_action

Review state

Markdown 內文不是正式 approval。只有 Apply bridge 寫入的 Decision Ledger event 才是正式決策。