SA260324R-0137
① SA Source
- Source: 開啟完整 SA 文章
- Section:
LPX Rack System - Line hint:
147
Context Before
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.
LPX Rack System
Evidence
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 ↗.
Context After
Source: SemiAnalysis Accelerator Model ↗
② Atomic Claim
SemiAnalysis 認為這個 server configuration 並不是 3Q 會出貨的版本，Nvidia 仍會進行修改。
- Epistemic Mode:
EXPECTED - Mapping Status:
PARTIAL
③ Semantic Frame
{
"attribute": "PRODUCTION_CONFIGURATION_CHANGE",
"context_nodes": [],
"entity": {
"id": "02_companies/NVDA",
"label": "Nvidia"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": "server configuration 的指涉依賴前文",
"numeric_mentions": [],
"temporal_mentions": [
"3Q"
]
},
"value": {
"numeric_mentions": [],
"value_text": "預期 3Q 出貨版本會與目前展示的 server configuration 不同，Nvidia 仍會修改。"
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| entity | Nvidia | NVDA |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
SemiAnalysis 認為這個 server configuration 並不是 3Q 會出貨的版本，Nvidia 仍會進行修改。
V2 Semantic Frame Draft
{
"attribute": "PRODUCTION_CONFIGURATION_CHANGE",
"context_nodes": [],
"entity": {
"id": "02_companies/NVDA",
"label": "Nvidia"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": "server configuration 的指涉依賴前文",
"numeric_mentions": [],
"temporal_mentions": [
"3Q"
]
},
"value": {
"numeric_mentions": [],
"value_text": "預期 3Q 出貨版本會與目前展示的 server configuration 不同，Nvidia 仍會修改。"
}
}V2 Revision Metadata Draft
{
"epistemic_mode": "EXPECTED",
"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 才是正式決策。