SA260324R-0345
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Cables and Connectors: Amphenol Continues to Benefit - Line hint:
437
Context Before
Next, we mentioned that a very high spec PCB is required for the LPX compute tray. We estimate that each compute tray main board PCB will carry $7k ASP. The suppliers for this are Victory Giant and WUS. Of course, there are several other PCB modules in the compute tray, but they do not need a high spec. Nvidia is continuing with their cable-less philosophy similar to the Vera Rubin compute tray which requires a lot of board-to-board connectors, which brings us to the next big beneficiary.
Cables and Connectors: Amphenol Continues to Benefit
Evidence
For the LPX, Amphenol will be a beneficiary for all the connectors for the backplane. Each LPX node requires 16 80DP Paladin connectors for the backplane. There are also board to board connectors required to connect all the various modules within the tray: the main LPU board with the host CPU module and the OSFP/QSFP modules that sit below the CPU module, the front-end NIC module, and the management module. Amphenol will supply the cable backplane too which is 8,160 DP per rack.
Context After
NVL288 System
For the Vera Rubin Ultra NVL288 System that we discussed above, we would say the cable backplane return for Kyber. If Rubin Ultra is deployed in such a form factor – each of the Rubin Ultra GPUs will have a scale-up bandwidth of 14.4Tbit/s uni-di, requiring 144 DPs of cables to connect to the NVSwitches. 144 DPs times 288 GPUs means a total of 41,472 DPs to connect this larger world size domain. This is a lot of cables, so it is more of an upper bound of how much cable content could be used here. If there is oversubscription or if the inter-rack connection is made through the switches – it is possible fewer DPs would be needed.
② Atomic Claim
- Epistemic Mode:
EXPECTED - Mapping Status:
PARTIAL
③ Semantic Frame
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "04_knowledge_base/Groq LPX",
"label": "LPX"
},
"role": "system"
},
{
"node": {
"id": "02_companies/APH",
"label": "Amphenol"
},
"role": "beneficiary"
},
{
"node": {
"id": "04_knowledge_base/Backplane",
"label": "backplane"
},
"role": "component"
}
],
"qualifiers": {
"condition_text": "generic connectors have no canonical entity; Expected LPX connector-content benefit",
"numeric_mentions": [],
"temporal_mentions": []
},
"relation_type": "LPX_BACKPLANE_CONNECTOR_BENEFICIARY"
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| system | LPX | 04_knowledge_base/Groq LPX |
| beneficiary | Amphenol | APH |
| component | backplane | Backplane |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
原文預期：在 LPX 中，Amphenol 會受益於 backplane 所需的 connector content。
V2 Semantic Frame Draft
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "04_knowledge_base/Groq LPX",
"label": "LPX"
},
"role": "system"
},
{
"node": {
"id": "02_companies/APH",
"label": "Amphenol"
},
"role": "beneficiary"
},
{
"node": {
"id": "04_knowledge_base/Backplane",
"label": "backplane"
},
"role": "component"
}
],
"qualifiers": {
"condition_text": "generic connectors have no canonical entity; Expected LPX connector-content benefit",
"numeric_mentions": [],
"temporal_mentions": []
},
"relation_type": "LPX_BACKPLANE_CONNECTOR_BENEFICIARY"
}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 才是正式決策。