SA260324R-0132

回到這篇 SA Coverage

① SA Source

Context Before

image

Source: SemiAnalysis

Evidence

For LPUs, deploying a draft model or MTP layers is quite different from applying AFD. FFNs are stateless, while draft models and MTP layers require dynamic KV cache loading. Each FFN is around hundreds of megabytes, whereas draft models and MTP layers take up tens of gigabytes. To support this memory usage, LPUs can access up to 256 GB of DDR5 per Fabric Expansion Logic FPGAs on the LPX compute tray.

Context After

LPX Rack System

Let’s look at the LPX rack system, which has interesting details. Nvidia has displayed an LPX rack with 32 1U LPU compute trays with 2 Spectrum-X switches. This 32 tray 1U version that Nvidia has shown off at GTC is very close to Groq’s original server design before the acquisition. We believe that this server configuration is not the version that will be shipped in 3Q, with Nvidia implementing changes. Here, we will detail what we know about the actual production version. This was already detailed in the Accelerator model ↗.

② Atomic Claim

In the source’s speculative-decode discussion, draft models and MTP layers occupy tens of GB, exceeding one LPU’s SRAM capacity.

  • Epistemic Mode: ASSERTED
  • Mapping Status: PARTIAL

③ Semantic Frame

{
  "frame_type": "CLAIM_ONLY",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [
      "tens of gigabytes"
    ],
    "temporal_mentions": []
  },
  "reason": "MIXED_MAPPED_AND_UNMAPPED_COMPONENTS_DRAFT_MODEL_HAS_NO_CANONICAL_ENTITY",
  "statement": "In the source’s speculative-decode discussion, draft models and MTP layers occupy tens of GB, exceeding one LPU’s SRAM capacity."
}

④ Canonical Entity Mapping

  • 此 CLAIM_ONLY revision 沒有 canonical Entity mapping。

⑤ V2 Draft(需要修正時直接編輯)

Inline repair

只編輯以下三個 Draft 區塊。完成後將 review_action 設為 REQUEST_REPAIR,再手動執行 Repair Preview。
執行腳本前,Draft 不會寫入 Claim Store 或 Graph。

V2 Atomic Claim Draft

In the source’s speculative-decode discussion, draft models and MTP layers occupy tens of GB, exceeding one LPU’s SRAM capacity.

V2 Semantic Frame Draft

{
  "frame_type": "CLAIM_ONLY",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [
      "tens of gigabytes"
    ],
    "temporal_mentions": []
  },
  "reason": "MIXED_MAPPED_AND_UNMAPPED_COMPONENTS_DRAFT_MODEL_HAS_NO_CANONICAL_ENTITY",
  "statement": "In the source’s speculative-decode discussion, draft models and MTP layers occupy tens of GB, exceeding one LPU’s SRAM capacity."
}

V2 Revision Metadata Draft

{
  "epistemic_mode": "ASSERTED",
  "mapping_status": "PARTIAL"
}

⑥ 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 才是正式決策。