Repository navigation
fix: rebuild Humming launcher with packed-scale shape metadata - #88
Conversation
|
Actual H100 controlled gate PASS on corrected image
Serving is proceeding to isolated same-corrected-image flag-off/on evaluation with default kernels. Full-model behavior, production-path performance and actual KV savings remain pending; no production adoption claimed. Raw evidence is retained in serving results/packdiag,packctl,packfix; earlier failed results are not erased by this pass. |
|
Full serving follow-up: same corrected image642dd15 (
Both: vision3/3,boundary8/8,needles2/2; full ladders completed. Acceptance audit from raw accept.json:
Assessment: recommend the opt-in for the separate daytime capacity-oriented rollout, accepting the observed1–3% decode cost for32% more KV capacity. Do not call that cost proven noise, claim bitwise full-output parity, or add the separate residual-buffer saving without a combined run. Production configuration and tonight's old-image restore are unchanged. Raw evidence retained by serving under results/packoff and results/packon. |
Actual GPU failure
The controlled H100 probe proved unpacked repeats exact with Stream-K off, then the packed launch failed native BS shape validation (1024 !=2048). The original image changed JIT scale storage but omitted native launcher geometry. No packed output pass exists yet. The previous no-native-rebuild assumption was wrong.
Fix
Addressing audit: launcher passes bs.data_ptr unchanged when TMA-BS is off; its TMA descriptor helper returns early. JIT global/shared copy strides use N/2 bytes per group and EGN/2 storage, while the scale reader expands each byte to the original two byte values. Shape correction matches those strides, not an oversized fake view.
Evidence / limits
24 CPU repository tests pass. Modified launcher compiled successfully in CPU-only audit container capped2 CPUs/4GiB RAM, no swap, one translation unit. Python compilation passed. Actual corrected-image GPU shape acceptance/output equality/graph replay and serving memory qualification remain pending. Default feature flags remain off. No GPU job launched from this session.
Source failure log retained by serving under results/packctl; do not treat controlled tests as production-default Stream-K qualification. No equality tolerances relaxed.