Repository navigation
Config: Expose exllamav3 draft_confidence option - #504
Merged
Merged
Conversation
Wire the Generator's draft_confidence parameter (target acceptance probability for dynamic draft truncation) through DraftModelConfig, the exllamav3 backend, model load requests, and the docs/samples.
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.
Wire the Generator's draft_confidence parameter (target acceptance probability for dynamic draft truncation) through DraftModelConfig, the exllamav3 backend, model load requests, and the docs/samples.
On my system I need at least an average draft confidence of 60% to benefit from speculative decoding.
By exposing this existing config option, I can make dynamic draft be more aggressive in trimming down the draft speculation length.