IX2-0534
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Core Changes Since InferenceXv1 - Line hint:
768
Context Before
Core Changes Since InferenceXv1
One of the main changes we have made since v1 is the cadence with which we perform sweeps. Previously, we were jestermaxing and performed a full sweep over each configuration nightly. However, as we added more chips, disaggregated prefill, wide EP, and other features, we realized that running every single night was way too time consuming and wasteful. Moreover, it’s just not necessary – benchmarks only really need to be re-run when recipes change or a new software version is released.
Evidence
When a developer makes a performance-impacting change to a given config, they add an entry to the changelog listing the affected config along with a brief description of the change
Context After
Below is a high-level diagram of how InferenceX launches jobs.
② Atomic Claim
關於 InferenceX：當開發者對特定 config 做出會影響效能的修改時，會在 changelog 新增一筆紀錄，列出受影響的 config 與變更簡述。
- Epistemic Mode:
ASSERTED - Mapping Status:
PARTIAL
③ Semantic Frame
{
"attribute": "UNSPECIFIED_ATTRIBUTE",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/InferenceX",
"label": "InferenceX"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [],
"value_text": "關於 InferenceX：當開發者對特定 config 做出會影響效能的修改時，會在 changelog 新增一筆紀錄，列出受影響的 config 與變更簡述。"
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| entity | InferenceX | InferenceX |
⑤ 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 才是正式決策。