VR2R-0088
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Rubin - Line hint:
125
Context Before
Transistor count has climbed 60% to 336 billion.
A notable omission from Rubin is the mention of Sparse FLOPs. In previous generations, 2:4 structured sparsity was used to double marketing FLOPs numbers. However, adoption was minimal especially at low precisions due to accuracy losses from the rigid sparsity structure forcing half of the values to be zero. Programmers basically ignored structured sparsity as it was not useful, which caused hardware designs to change as well. Blackwell Ultra GB300 added 50% more dense FP4 while keeping sparse FP4 FLOPs the same, while AMD’s MI355X stopped supporting structured sparsity on MXFP8, MXFP6 and MXFP4 formats to save silicon area.
Evidence
Rubin’s adaptive compression engine in the improved Transformer Engine is a key feature to re-boost naturally sparser inference performance by doing dynamic computation of sparsity in-flight and eliminating zeros in the data stream without zeroing out non-zero values, thus maintaining model accuracy while still boosting performance. This is done automatically on existing models built for Blackwell without the need for a new programming model or specific optimizations. While models that utilize Post Training Quantization or Quantization Aware Training will be tuned to maximize adaptive compression speedups, they are not strictly needed to take advantage of dynamic compression.
Context After
This means the sparser the workload, the closer the performance will be to the 50 PFLOPS marketed peak performance. NVIDIA thus brands the 50 PFLOPS figure as FP4 Inference while the 35 PFLOPS FP4 Training number is for dense workloads. As accuracy is preserved, this allows the marketing team to claim 5x FLOPs for Rubin over GB200, comparing 50 PFLOPS dynamically compressed FP4 to 10 PFLOPS dense FP4. Whether actual GEMM performance reaches 50 PFLOPS depends on how many zeros are in the tensor. The more zeros, the closer it can reach. The less zeros in the tensor, the lower the speedup. Overall, we expect to see much greater traction for Rubin’s adaptive sparsity compression as opposed to structured sparsity thanks to the automatic implementation.
With that said, many ML Systems engineer are still skeptical that this new form of sparsity will work well, and it is very possible that Nvidia’s 50 PFLOPS is purely marketing like prior generations
② Atomic Claim
Rubin 改良版 Transformer Engine 中的 adaptive compression engine，會在資料流中即時動態計算 sparsity 並消除 zeros，但不把非零值強制歸零，因此可維持 model accuracy，同時提升天然較 sparse 的 inference performance。
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "04_knowledge_base/Vera Rubin",
"label": "Rubin"
},
"role": "platform"
},
{
"node": {
"id": "04_knowledge_base/Transformer Engine",
"label": "Transformer Engine"
},
"role": "engine"
},
{
"node": {
"id": "04_knowledge_base/Sparsity",
"label": "sparsity"
},
"role": "sparsity_mechanism"
}
],
"qualifiers": {
"condition_text": "dynamic in-flight zero elimination without zeroing non-zero values",
"numeric_mentions": [],
"temporal_mentions": []
},
"relation_type": "ADAPTIVE_COMPRESSION_SPARSE_INFERENCE_MECHANISM"
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| platform | Rubin | 04_knowledge_base/Vera Rubin |
| engine | Transformer Engine | 04_knowledge_base/Transformer Engine |
| sparsity_mechanism | sparsity | Sparsity |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
Rubin 改良版 Transformer Engine 中的 adaptive compression engine，會在資料流中即時動態計算 sparsity 並消除 zeros，但不把非零值強制歸零，因此可維持 model accuracy，同時提升天然較 sparse 的 inference performance。
V2 Semantic Frame Draft
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "04_knowledge_base/Vera Rubin",
"label": "Rubin"
},
"role": "platform"
},
{
"node": {
"id": "04_knowledge_base/Transformer Engine",
"label": "Transformer Engine"
},
"role": "engine"
},
{
"node": {
"id": "04_knowledge_base/Sparsity",
"label": "sparsity"
},
"role": "sparsity_mechanism"
}
],
"qualifiers": {
"condition_text": "dynamic in-flight zero elimination without zeroing non-zero values",
"numeric_mentions": [],
"temporal_mentions": []
},
"relation_type": "ADAPTIVE_COMPRESSION_SPARSE_INFERENCE_MECHANISM"
}V2 Revision Metadata Draft
{
"epistemic_mode": "ASSERTED",
"mapping_status": "COMPLETE"
}⑥ 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 才是正式決策。