docs(models): record full glm-5.3 checkpoint screening - #406
Draft
earlvanze wants to merge 3 commits into
Draft
Conversation
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.
Scope
Record the full LibertAIDAI/GLM-5.3-NVFP4 checkpoint on the existing glm_moe_dsa path, preserving GLM-5.2 aliases, with config regression coverage and measured Vast screening evidence. This is full GLM-5.3, not Flash.
Measured evidence
One RTX PRO 6000 Blackwell Max-Q 96 GB, driver 595.84, Ubuntu 24.04.3, 36.48 effective CPU cores and a 1.87 TiB container memory limit. Runtime commit 55120d9. The report includes the exact inspected launch command and immutable links to all raw request results.
Initial 32-token direct-worker screen: c8 3.937 aggregate output tok/s; c16 offered against eight running slots 6.297. All 24 requests truncated during reasoning; zero final coding answers. Neither result qualifies the requested c8 target. A separate arithmetic smoke returned the correct answer but exposed a reasoning-parser formatting issue.
Verification and remaining work
Locally ran server tests plus the new model-config tests: 541 passed. That run included a separately prepared, uncommitted parser fix; this PR does not include that fix and does not claim patched-runtime validation.
Draft: longer repeated benchmarks, final-answer checks, actual serverless routing and idle/cached-restart lifecycle remain pending. No production-readiness or per-user 15 tok/s claim. No performance-engine change or A/B speedup claim.
AI-assisted under operator direction; preliminary evidence is intentionally retained, including failures.