[GLM-5.2 GB200] Preserve draft precision and disable background UCX progress / [GLM-5.2 GB200] 保留 draft 精度并关闭 UCX 后台进展 - #3401
edwingao28 wants to merge 1 commit into
Conversation
|
Thanks for the contribution!
中文感谢你的贡献!
|
91efe8b to
e908cc4
Compare
|
View unofficial run (performance): https://inferencex.semianalysis.com/inference?unofficialRun=36538876933 View unofficial run (accuracy): https://inferencex.semianalysis.com/evaluation?unofficialRun=36538876933 |
68d3ce2 to
274c69d
Compare
|
Sorry, over the weekend, there was 2 major refactors to clean up the technical debt accumalated over the past 11 months of moving at the speed of light. We don't see any major refactors in the forthseeable future besides cleaning up AMD multinode AgentX pile of bash. As much, due to the refactors, u would need to ask your agent to rebase from remote main@latest. Thank you in advance for ur understanding |
6113b30 to
fca8de5
Compare
…refill Keep the draft at shipped precision and disable only the two background UCX progress controls for disaggregated prefill. Preserve images, workload, strict synchronization and golden acceptance. Request the scoped engine-patch waiver. 保留 GLM-5.2 GB200 draft 的原始精度,仅关闭分离式 prefill 的两项 UCX 后台进展控制;保留镜像、工作负载、严格同步及 golden acceptance,并申请对应补丁例外。
fca8de5 to
9fbe9bf
Compare
|
Heads-up: #3576 (merged) replaced the bash launchers with a Python launcher, so this PR will conflict when you merge |
Description
Keep the draft at shipped precision. Disable background UCX progress only for GB200 disaggregated prefill; retain images, workload and golden acceptance.
Testing: Changelog, native matrix and setup selection pass; Full sweep started; results pending.
Blocker: Engine-patch waiver requires reviewer approval.
中文
使 draft 保持原始发布精度,仅关闭 GB200 分离式 prefill 的 UCX 后台进展;保留镜像、工作负载及 golden acceptance。
测试: changelog、原生矩阵及 setup 选择验证通过;完整 sweep 已启动,结果待验证。
阻塞: 补丁例外仍需审阅者批准。
AI 模型: Claude Opus 5.5 (
claude-opus-5-5) 完成初始实施与起草;GPT-6(具体版本不可确认)完成恢复、验证和委派复核。AI model disclosure
claude-opus-5-5): initial implementation/drafting.Related Issue
Related to #3228. / 关联 #3228。
Type of Change
Checklist
inferencex-e2e/perf-changelog.yamland have not edited historical entriesOWNER/MEMBER/COLLABORATOR) has commented/use <run_id>(or the legacy/reuse-sweep-run) on this PR. Do this only once there is a final full sweep that is all green with evals passing, since after this comment the sweep label will no longer automatically kick off new sweeps. Remove and re-add the label to force one.