Skip to content

Reduce one step decode for draft model.#11561

Merged
hnyls2002 merged 5 commits intomainfrom
lsyin/reduce-draft-steps
Oct 14, 2025
Merged

Reduce one step decode for draft model.#11561
hnyls2002 merged 5 commits intomainfrom
lsyin/reduce-draft-steps

Conversation

@hnyls2002
Copy link
Copy Markdown
Collaborator

@hnyls2002 hnyls2002 commented Oct 13, 2025

This PR introduces the DraftBackendFactor class to dispatch the mult-step draft decode backend. In any case, the draft backend only initializes attention backends for speculative_num_steps - 1 times.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @hnyls2002, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request streamlines the speculative decoding process for draft models by adjusting the iteration count in several attention backend modules. The change uniformly reduces the number of steps by one, aiming to optimize performance or correct an indexing issue related to speculative_num_steps. This ensures that the system correctly handles the intended range for speculative operations.

Highlights

  • Speculative Decoding Step Reduction: The number of speculative decoding steps for draft models has been reduced by one across multiple attention backend implementations.
  • Consistent Loop Adjustment: All modifications involve changing range(self.speculative_num_steps) to range(self.speculative_num_steps - 1) in relevant loops, ensuring a uniform adjustment.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly reduces the number of draft decoding steps by one across various attention backend implementations. The change from range(self.speculative_num_steps) to range(self.speculative_num_steps - 1) aligns with the logic of speculative decoding, where speculative_num_steps - 1 draft tokens are generated. The fix is applied consistently in most files. However, I've pointed out a potential incomplete fix in trtllm_mha_backend.py where other methods might still contain the original buggy loop range, which could lead to an IndexError.

Comment thread python/sglang/srt/layers/attention/trtllm_mha_backend.py
@hnyls2002 hnyls2002 merged commit 5ea96ac into main Oct 14, 2025
27 of 44 checks passed
@hnyls2002 hnyls2002 deleted the lsyin/reduce-draft-steps branch October 14, 2025 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants