Repository navigation
Use cuDNN for Qwen3.8-27B long-context training - #3
Merged
Merged
Conversation
Select native cuDNN THD with CP2 and allow cold TP engine initialization. Validate observed attention against the saved configuration, rejecting backend mismatches while retaining full-context capacity requirements.
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.
Outcome
Use native cuDNN THD attention with CP2 for the Qwen3.8-27B long-context recipe. The capacity audit checks that the observed backend matches the saved configuration while retaining the full 261,888-token requirements. Allow cold TP engine compilation during initialization.
Verification
Compatibility and provenance
The launcher ID remains
qwen27b-long. Direct YAML users should useconfigs/recipes/qwen3_8_27b_256k_cudnn_cp2_nvlink.yaml. Explicit FA4 configurations remain supported by the audit. Checkpoint and export formats are unchanged; existing AngelSpec attribution is retained.