Skip to content

[DNM, Experimental] feat(bench): GLM-5.3-Flash GB300 FP8 HiCache concurrency / [DNM, Experimental] feat(bench): GLM-5.3-Flash GB300 FP8 HiCache 并发 - #4732

Draft
functionstackx wants to merge 3 commits into
feat/glm53flash-fp8-gb300-sglangfrom
feat/glm53flash-fp8-gb300-hicache-concurrency
Draft

functionstackx wants to merge 3 commits into
feat/glm53flash-fp8-gb300-sglangfrom
feat/glm53flash-fp8-gb300-hicache-concurrency

Conversation

@functionstackx

Copy link
Copy Markdown
Collaborator

Experiment

This draft is a child of PR #4715, preserving passing parent head c611580c42f9f8975d260d1a0a567c38e188d7d8. It adds matched OFF/HiCache-ON AgentX points at concurrency 40, 48, 56, 64, and 80, plus a dedicated ON canonical-evaluation selector.

Both arms keep the parent's official immutable SGLang v0.5.22-cu130 image, native FP8 checkpoint, TP4/EP1, full 1,048,576-token context, full 393-entry corpus, 3,600-second duration, FP8 E4M3 KV cache, and embedded EAGLE MTP 5/1/6. There is no max-running-requests override: the parent's observed server cap was 48, so higher client concurrency includes queued load rather than promising that many resident requests.

Only the ON recipe adds hierarchical caching with hicache-host-memory-fraction: 0.90, write_through, kernel I/O, and page_first layout. No fixed host size/ratio, engine patch, draft-precision override, or workload reduction is introduced.

Source and memory qualification

Exact source baa9befa381511cd4d56f83980951e5a45fffc6d includes the required hybrid INDEXER fix, compressed-page ownership fix, and hybrid MLA load-back wait. Matching target/draft KV pools use the existing packed host path; this source audit is not GPU host-restore correctness proof.

The builtin automatic allocator uses live available memory and cgroup room, a 10 GiB node reserve, local-rank sharing, 5% sizing slack, and a shared host allocation budget. No explicit size/ratio is set, avoiding the fixed-size INDEXER-budget problem described in open PR #42918.

dram-utilization: 1.0 is the existing nominal eligible offload-budget metadata, not the allocator's 0.90 fraction, actual pinned-memory use, or an additional Slurm RAM reservation. OFF rows retain the generator's zero offload-budget metadata; both arms preserve identical parent Slurm resources. Actual resolved host ratio, pool bytes, available/cgroup memory, and NUMA placement still need runtime evidence.

Validation and dispatch gate

  • Generated ten bound performance recipes and the dedicated ON evaluation recipe.
  • Passed 265 focused generation, acceptance, eval-path, and schema-validation tests.
  • No child GPU results exist. Keep this PR draft and all three GPU activation labels absent until the matrix and real-host-restore diagnostic are reviewed.

The current workflow selects one global minimum-concurrency canary, not one canary per OFF/ON arm. The performance changelog block disables eval selection, and a separate ON eval-only block prevents same-concurrency OFF/ON eval deduplication from silently choosing OFF.

Real host-restore qualification is pending. An isolated EVAL_ONLY prelude must prove an actual host-only restore with simulation absent, compatible target/draft INDEXER and recurrent-state transfers, and deterministic parity before clearing diagnostic cache state and running the unchanged canonical evaluation. A missing host hit is inconclusive, not a pass; ordinary GSM8K alone cannot rule out the reported restore defects.

The parent also had unresolved empty-stream request errors, so subsequent frontier comparisons must preserve phase-separated warmup/profiling errors and completion counts. No error-free or improved-frontier claim is made here.

AI model disclosure

GPT-6 Astra researched the pinned SGLang host-cache paths, prepared this GB300 FP8 child configuration, and ran local validation. The source audit was coordinated with other lane owners; no GPU measurements were fabricated.

中文

本草稿直接基于 PR #4715 的已通过提交,新增并发 40、48、56、64、80 的 OFF/HiCache-ON 成对实验,并提供独立的 ON 标准评测配置。保留官方不可变镜像、原生 FP8、TP4/EP1、完整 1,048,576-token 上下文、393 条目语料、3,600 秒时长及 EAGLE MTP 5/1/6。

ON 仅启用 HiCache、0.90 自动主机内存比例、write_through、kernel 和 page_first,不设置固定容量或比例,不修改引擎、推测头精度或工作负载。dram-utilization: 1.0 是原有 nominal offload-budget 元数据,不代表实际 pinned memory 或新增 Slurm 内存预留;OFF 的零值表示没有 offload budget,不表示未分配物理主机内存。

已生成十个性能配置和独立 ON 评测配置,并通过 265 项本地定向测试。当前没有新的 GPU 结果,保持 draft 且不添加 GPU 激活标签,待矩阵和真实 host-only restore 诊断完成审查。现有 workflow 只有一个全局最低并发 canary,不能据此声称 OFF/ON 均已通过独立 canary。

真实 restore 诊断必须在关闭模拟接受率的独立评测分配中证明 host read、INDEXER/循环状态正确传输及确定性结果一致,然后清空诊断缓存并执行原始标准评测。没有实际 host hit 属于诊断不充分,不能视为通过;当前也不声称无错误或性能前沿已经改善。

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Thanks for the contribution!

  • Review: If this PR changes files owned by someone other than a repository admin or @SemiAnalysisAI/core, ask one eligible CODEOWNER to complete the latest PR_REVIEW_CHECKLIST.md before contacting a core maintainer on Slack. Follow the template exactly, including As a PR reviewer and CODEOWNER, I have reviewed this and have, so sign-off verification triggers.
  • PR verification: Sweeps run only when the PR appends an inferencex-e2e/perf-changelog.yaml entry and carries exactly one primary label: full-sweep-fail-fast (strongly recommended; canary plus per-matrix fail-fast), full-sweep-enabled (canary; matrix jobs continue after a failure), or non-canary-full-sweep-enabled (no canary or fail-fast). The modifiers all-evals, evals-only, and agentx-fast require a primary label. On fork PRs, a maintainer applies the label. See sweep labels and reuse.
  • After merging: PR authors must ensure all GitHub Actions jobs pass. Transient failures often pass on rerun; see how to rerun failed jobs.
中文

感谢你的贡献!

  • **审阅:**如果 PR 修改的文件归属于仓库管理员及 @SemiAnalysisAI/core 之外的 CODEOWNER,请先联系一位有资格的 CODEOWNER 填写最新的 PR_REVIEW_CHECKLIST.md,再通过 Slack 联系核心维护者。必须严格遵循模板,并保留 As a PR reviewer and CODEOWNER, I have reviewed this and have,才能触发签核验证。
  • **PR 验证:**只有当 PR 在 inferencex-e2e/perf-changelog.yaml 末尾追加了条目,并且恰好带有一个主标签时,才会运行扫描:full-sweep-fail-fast(强烈推荐;canary 加逐矩阵 fail-fast)、full-sweep-enabled(有 canary;矩阵任务在失败后继续运行)或 non-canary-full-sweep-enabled(无 canary,也无 fail-fast)。修饰标签 all-evals、evals-only 和 agentx-fast 必须与主标签一起使用。fork PR 的标签由维护者添加。参见扫描标签与复用。
  • **合并后:**PR 作者必须确保所有 GitHub Actions 任务通过。临时性失败通常可以通过重新运行恢复;参见重新运行失败任务的说明。

@functionstackx functionstackx changed the title [DNM, Experimental] feat(bench): GLM Flash GB300 FP8 HiCache frontier / [DNM, Experimental] feat(bench): GLM Flash GB300 FP8 HiCache 前沿 [DNM, Experimental] feat(bench): GLM-5.3-Flash GB300 FP8 HiCache concurrency / [DNM, Experimental] feat(bench): GLM-5.3-Flash GB300 FP8 HiCache 并发 Nov 1, 2026
@functionstackx functionstackx added the full-sweep-fail-fast Full sweep with canary gate; first failure cancels the rest of that matrix (recommended) label Nov 1, 2026
@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

full-sweep-fail-fast Full sweep with canary gate; first failure cancels the rest of that matrix (recommended)

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant