2025-12-04_aws-trainium3-deep-dive-a-potential::TRN3-0005
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Amazon Basics GB200 aka GB200-at-Home - Line hint:
57
Context Before
On the systems and networking front, AWS is following an “Amazon Basics” approach that optimizes for perf per TCO. Design choices such as whether to use a 12.8T, 25.6T or a 51.2T bandwidth scale-out switch or to select liquid vs air cooling are merely a means to an end to provide the best TCO for the given client and the given datacenter.
For the scale-up network, while Trn2 only supports a 4x4x4 3D Torus mesh scaleup topology, Trainium3 adds a unique switched fabric that is somewhat similar to the GB200 NVL36x2 topology with a few key differences. This switched fabric was added because a switched scaleup topology has better absolute performance and perf per TCO for frontier Mixture-of-Experts (MoE) model architectures.
Evidence
Even for the switches used in this scale-up architecture, AWS has decided to not decide: they will go with three different scale-up switch solutions over the lifecycle of Trainium3, starting with a 160 lane, 20 port PCIe switch for fast time to market due to the limited availability today of high lane & port count PCIe switches, later switching to 320 Lane PCIe switches and ultimately a larger UALink to pivot towards best performance.
Context After
Amazon’s Software North Star
On the software front, AWS’s North Star expands and opens their software stack to target the masses, moving beyond just optimizing perf per TCO for internal Bedrock workloads (ie DeepSeek/Qwen/etc which run a private fork of vLLM v1) and for Anthropic’s training and inference workloads (which runs a custom inference engine and all custom NKI kernels).
② Atomic Claim
Trainium3 lifecycle 規劃三代 scale-up switch：160-lane/20-port PCIe → 320-lane PCIe → 高 radix UALink。
- Epistemic Mode:
EXPECTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"attribute": "scale_up_switch_roadmap",
"context_nodes": [
{
"id": "04_knowledge_base/PCIe",
"label": "PCIe"
},
{
"id": "04_knowledge_base/UALink",
"label": "UALink"
}
],
"entity": {
"id": "04_knowledge_base/Trainium",
"label": "Trainium3"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [
"160",
"20",
"320"
],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [
"160",
"20",
"320"
],
"value_text": "160-lane 20-port PCIe -> 320-lane PCIe -> larger UALink"
}
}④ Canonical Entity Mapping
⑤ 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 才是正式決策。