Repository navigation
exp: validate EOS-aware four-model GPU RNGD ATOM handoff - #228
Draft
gspark-etri wants to merge 6 commits into
Draft
gspark-etri wants to merge 6 commits into
gspark-etri wants to merge 6 commits into
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.
Background
Fixed-length repeated-capital fixtures do not establish normal chat stopping or answer quality. The four-model goal needs diverse prompts, shared exact input IDs and explicit separation of token parity from factual correctness.
Changes
Verification
Base b131963, native evidence e16c256, RNGD handoff implementation5e19f0e, medium-context evidence c645fff. A10080GB BF16 SDPA; exclusive ATOM B1/context9216, Rebel0.11/Optimum0.11.0.post1. Gemma global+sliding corrected artifact; Qwen k3, KONI k1. Checkpoint SHAs and commands in the experiment record.
-192 completed runs:4models ×2backends ×12cases ×2repeats. All terminate at EOS;96 repeat pairs exact.
Compatibility and limits
Research runner only: production HTTP stopping was not changed. Direct native GPU/ATOM graphs and short and medium-context RNGD full-prefix handoff, static B1; no production PD serving measurement or genuine producer/transfer overlap. Timings are observations, not controlled end-to-end performance claims. Four questions and repetitive context are diagnostic fixtures, not a general quality benchmark. Broader numerical analysis, long RNGD semantic inputs, production cache/cancellation and compute/transfer overlap remain open.
Related Issue
Related #227 and #201. Stacked on #226 (exp/225-gemma-global-causal).
Generated with Codex; maintainer review and merge required.
Long semantic results (14d9772; all four models)
KONI and Qwen3-0.6B pass16/16 GPU/ATOM comparisons at approximately6K input tokens. Gemma at6423–6428 tokens passes3/4 GPU and4/4 ATOM comparisons, Qwen3-4B also passes4/4 on each decoder, for31/32 total across all four models. The original queue completed with48producer runs and exited0. All tested52/56/64/72KV slot readbacks are exact.
Preserved failure: long arithmetic yields30 on nativeGPU BF16/FP32 but25 with RNGD prefill on either decoder; nativeATOM also25. Both are wrong. The same Gemma layer equations executed on GPU choose3 as first token at BF16/FP32, while RNGD chooses2. Intermediate KV differences grow by layer. Cause is unresolved and tracked in #233; no transport-correctness or quality-pass inference is made from native/imported agreement. Reusable check_gemma_equations.py, exact commands, output JSON and the failed comparison are included.
Full-prefix host staging only; live production PD, overlap and sustained serving performance remain outside the demonstrated results.