NIEK2-0076
① SA Source
- Source: 開啟完整 SA 文章
- Section:
SRAM and Memory Hierarchy - Line hint:
69
Context Before
Source: Nvidia
Evidence
Context After
One of the benefits of relying on SF4 is that it isn’t constrained like TSMC’s N3, which is putting a cap on accelerator production and is a key reason why the industry remains compute constrained. ↗ This is in addition to not having HBM which is also constrained ↗. This allows Nvidia to ramp production of the LPU without sacrificing or eating into their valuable TSMC allocation or HBM allocations, representing true incremental revenue and capacity that noone else can access.
Since Nvidia has taken over, the next generation LP40 will be fabricated on TSMC N3P and use CoWoS-R, and Nvidia will contribute more of their own IP such as supporting the NVLink protocol rather than Groq’s C2C. This will be the first LPU to be extremely co-designed alongside the Feynman platform. Groq’s original plans for LPU Gen 4 was also with TSMC and Alchip as the back-end design partner. Alchip’s involvement is now redundant with Nvidia able to perform backend design on their own. One of the technical innovations planned is hybrid bonded DRAM to extend on-chip memory with only a slight decrease in latency and bandwidth vs SRAM, but much higher performance compared to DRAM. SK Hynix was tapped as the supplier of the DRAM to be used for the 3D stacking. All of this and more was detailed long ago in the Accelerator model ↗.
② Atomic Claim
只有很小一部分面積配置給 MatMul 核心，可提供 1.2 PFLOPs 的 FP8 運算能力，遠低於 Nvidia GPUs。
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"comparison_expression": "只有很小一部分面積配置給 MatMul 核心，可提供 1.2 PFLOPs 的 FP8 運算能力，遠低於 Nvidia GPUs。",
"entities": [
{
"id": "04_knowledge_base/FP8",
"label": "FP8"
},
{
"id": "02_companies/NVDA",
"label": "Nvidia"
},
{
"id": "04_knowledge_base/GPU",
"label": "GPUs"
}
],
"frame_type": "COMPARISON",
"metric": "COMPUTE_PERFORMANCE",
"operator": "LESS_THAN",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [
"1.2 PFLOPs"
],
"temporal_mentions": []
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| comparison_entity_0 | FP8 | FP8 |
| comparison_entity_1 | Nvidia | NVDA |
| comparison_entity_2 | GPUs | GPU |
⑤ 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 才是正式決策。