Add exact GLM-5.3 adaptive MTP and DFlash7 SparkCache runtimes - #143
Closed
FujitsuPolycom wants to merge 1 commit into
Closed
Add exact GLM-5.3 adaptive MTP and DFlash7 SparkCache runtimes#143FujitsuPolycom wants to merge 1 commit into
FujitsuPolycom wants to merge 1 commit into
Conversation
This was referenced Aug 30, 2026
Owner
Author
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.
Resulting behavior
This PR adds two reproducible ARM64 GLM-5.3 runtime compositions that use the same exact vLLM Python source, B12X kernels, fast tensor loading, and SparkCache integration:
Each builder verifies the retained compiled vLLM and CUDA components, the overlaid Python source, B12X source, SparkCache source, patch set, generated artifacts, and image labels before producing an image. Executable four-rank profiles and operator quickstarts cover ordinary safetensors and fastsafetensors loading. Runtime messages and configuration use SparkCache CUDA restore and SparkCache CUDA placement terminology.
The DFlash7 profile removes unused DeepEP, disables unsupported symmetric-memory and FlashInfer all-reduce probes, disables all-reduce RMS fusion, and selects language-model-only serving. ModelOpt and FP8 KV warnings remain visible because they describe real runtime limitations.
Status
Compatibility
The DFlash7 profile binds SparkCache commit
5ec6a9953ad5d39120298bbfc26e95a6fa4b1dc3, tree94c236b9dfbf5f70075eb47877fd9caaa5d8c249, and source SHA-256bc238f96e550c7ec27d4081dd1f2e741d404aaf5c8572d89ccc5e76812be4d63. That commit is the head of SparkCache consolidation draft PR #32.The runtime compositions use distinct served-model names, cache roots, JIT roots, and runtime identities. Existing deployment profiles remain available. Stored state is accepted only when the complete model, topology, vLLM, B12X, SparkCache, KV layout, and runtime-option identity matches; other entries are rejected and recomputed.
Validation
This PR consolidates the implemented runtime surface previously presented across draft PRs #129, #130, #131, #134, #136, #137, #139, #140, and #141. Direct-fabric image distribution, runtime evidence, adaptive-versus-DFlash diagnostics, and recurrent-boundary metadata remain independent review units.