Repository navigation
RC4.1: faster prose and code decode, bit-exact with RC2; long GLM tool calls fixed - #46
Merged
Merged
Conversation
…ed MoE route and MLA front, dense TP split, selector top-k, MXFP8 tiles, DFlash2 edge 0.6 and NVFP4 conv twins The pinned tree (ae5e79f8) equals exp/prose-rc4 c6089633, the candidate measured on the pair. All three profiles gain the eleven switches it was measured with. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…/ 61.4), bit-exact with RC2 results/2026-10-12-rc4: 12-prompt C1 decode, strict prose bursts, logprob hash 246cd1331b41, 524/524 outputs identical to RC2, C4 == C1, and the four-session 204K fill (12/12) from the LLooM deployment. README: this release's receipts link and the single-stream decode row. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…x, quality) RigMark decode 72.3 / 38.3 / 91.7 tok/s (RC2 65.5 / 36.5 / 88.8), short-code 2-stream aggregate 60.5 (55.2), matrix 132.1 s (136.3), field guide 49.5 / 76.3 s (49.9 / 77.3); prefill and staggered TTFT unchanged. README rows updated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…han 1024 tokens are no longer cut The envelope-stuck guard recognized parameter values only by Qwen's <parameter=...> ids, so long GLM tool calls ended with finish_reason length and no call. Upstream fix ade7b012 on upstream/glm53-flash 0b515eec, layer re-applied (301479a2, tree ac5a080b). Profiles unchanged; RC4's speed receipts stand (decode path unchanged). RESULT.md gains an RC4.1 section. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…gMark Quality before/after Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
data-angel
added a commit
to Enntity/lloom
that referenced
this pull request
Oct 12, 2026
…t 401a5c27 Enntity/sparkglm#46 merged as 401a5c27; its install tree is unchanged (cfb463a952b5), so the image, tag and digest stay the same. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
RC4.1 hotfix (current pin). The engine is Enntity/atlas
sparkglm/atlas-20261012-rc4.1-layered@301479a2(treeac5a080b). The image isghcr.io/enntity/atlas-sparkglm:cfb463a952b5(sha256:0ddea7cdb372e4407db63dc4f2b5b1a08b4576b8223ded6a4fca3463439ccfb2), install treecfb463a952b517b87baf302b5b3b279a115c5626. It is staged on both pair hosts and not yet deployed.The bug. The envelope-stuck guard (
MAX_TOOL_BODY_TOKENS= 1024) recognized parameter values only by Qwen's<parameter=…>token ids. Every GLM tool call longer than about 1,024 tokens therefore ended withfinish_reason"length" and no tool call. The bug has been present since before RC2.The fix (
ade7b012onfix/glm-tool-value-markers, on top ofupstream/glm53-flash0b515eec): the engine resolves GLM's single-token<arg_value>/</arg_value>at startup and tracks value bodies by them. Sampling is unchanged.Layering. The seven SparkGLM-only layer commits are re-applied on top of the fix. The first of them (
661a26a0) now declares the KV-shard flag its native bridge reads, which upstream7e13c1bbremoved.Against RC4's measured tree (
5c523903/ae5e79f8), the pin adds exactly two things, and neither touches the decode path:The speed and exactness receipts in
results/2026-10-12-rc4/were measured on RC4.RESULT.mdhas an RC4.1 section. Live gate results will be added after the deploy.Profiles are unchanged from RC4.
RC4 moves the engine to Enntity/atlas
sparkglm/atlas-20261012-rc4-layered@5c523903. That is the upstream candidateupstream/glm53-flash-20261012-rc4@ad047638plus the unchanged SparkGLM-only layer. Its treeae5e79f8is identical toexp/prose-rc4@c6089633, the build measured on the pair.The image is
ghcr.io/enntity/atlas-sparkglm:846ee9e1e501(sha256:88461891963193b8e2abf0cb1cd603bf31fd9e3a8e1422074d10dd46f886485f). The install tree is846ee9e1e501eaf7afb71211aa2473d9610b2344. It is deployed on the pair through LLooM.Install. All three profiles add ten engine switches and one profile switch:
ATLAS_RDMA_ONESHOT_SM_STAGE=1ATLAS_GLM_MOE_ROUTE_FUSE=1ATLAS_GLM_DENSE_TP_SPLIT=1ATLAS_GLM_KDA_COMMIT_CTAS=96ATLAS_GLM_DRAFT_TP_TOPK=1ATLAS_DFLASH_ASYNC_UPLOADS=1ATLAS_GLM_MLA_FUSE=1ATLAS_GLM_MXFP8_TILED=1ATLAS_DFLASH2_EDGE=0.6ATLAS_DFLASH_CONV_TWIN=nvfp4ATLAS_DFLASH_CONF_PROBE=256(the profile switch)With
SPARKGLM_KV_SHARD=1, the 4x1m environment equals the tested dev profile exactly. Only 4x1m was measured.install/atlas-source.jsonpins5c523903and records the layers.Results (
results/2026-10-12-rc4/; raw receipts with SHA256SUMS). All results are bit-exact with RC2:Exactness evidence:
246cd1331b41is unchanged;README numbers changed:
Later upstream fixes, not in this release. The upstream branch
upstream/glm53-flash-20261012-rc4(andupstream/glm53-flash, fast-forwarded to it) now carries four CI-only fix commits on top ofad047638. None of them changes GB10 runtime behavior. The only runtime-source edit removes a variable nothing reads on that branch. They are:7e13c1bbdrops the unusedshardedflag inpaged_glm.rs. Only the SparkGLM layer reads it, so the next re-layer must declare it inside the layer commit.bc9d0de4replaces themxfp8_tile16intra-doc link with plain code.a6f35bf7mirrors theDF2_SEL_EDGEtwin into the strix-hip selector copy.0b515eecapplies rustfmt tocanonical_verify_gpu_tests.rs.RC4 pinned the tested tree at
5c523903. RC4.1 (above) builds onupstream/glm53-flashwith these four commits included.After merge: in LLooM
atlas-sparkglm-rc4(Enntity/lloom#64), replace the SparkGLM revision35dc1b41c92351d09d47af64e69b44b3393e2334(and its short form35dc1b41) with the merge commit. It appears in the pin, recipe, docs and test files thattools/lloom_pin_rc41.pyrewrites. The tree, tag and digest stay the same.🤖 Generated with Claude Code