NIEK2-0035
① SA Source
- Source: 開啟完整 SA 文章
- Section:
LPU chip - Line hint:
43
Context Before
Source: Groq, SemiAnalysis
The data flow and instruction flow design requires fine-grained pipelining to achieve high performance. Since LPU architecture makes computation deterministic, the compiler can aggressively schedule and overlap instructions to hide latency. The LPU’s use of high bandwidth SRAM and aggressive pipelining are the two main factors that enable LPU’s low latency.
Evidence
LPU gen 1 was designed on a legacy Global Foundries 14nm process
Context After
One of the selling points is that the chip can be manufactured and packaged entirely in the United States compared to their competitors being heavily reliant on the Asia semiconductor supply chain: logic and packaging in Taiwan, with HBM from Korea.
Since then, Groq’s roadmap has stalled due to execution, with no LPU 2 having been shipped. This leaves the Groq LPU looking even more dated against competing roadmaps. What was once a meaningful but still manageable node disadvantage versus 7nm-era peers has widened into a far sharper gap, with all leading accelerator platforms now moving onto 3nm-class processes in 2026.
② Atomic Claim
第一代 LPU 採用較舊的 Global Foundries 14nm 製程設計。
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "04_knowledge_base/Groq LPU",
"label": "LPU"
},
"role": "user_or_subject"
},
{
"node": {
"id": "02_companies/GlobalFoundries",
"label": "Global Foundries"
},
"role": "used_entity"
},
{
"node": {
"id": "04_knowledge_base/14nm",
"label": "14nm"
},
"role": "used_entity"
}
],
"qualifiers": {
"condition_text": null,
"numeric_mentions": [
"14"
],
"temporal_mentions": []
},
"relation_type": "USES"
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| user_or_subject | LPU | 04_knowledge_base/Groq LPU |
| used_entity | Global Foundries | GlobalFoundries |
| used_entity | 14nm | 14nm |
⑤ 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 才是正式決策。