Skip to content

Opt:ascend kv separation; dsv3 support graph; fused dequant+swiglu+quant #9355

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

chenxu140
Copy link
Contributor

Motivation

Modifications

Accuracy Tests

Benchmarking and Profiling

Checklist

Copy link
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.

Summary of Changes

Hello @chenxu140, 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 introduces significant optimizations for SGLang's performance on Ascend NPUs. The core changes involve a fundamental redesign of the Key-Value (KV) cache to store Key and Value components separately, enhancing memory efficiency and data transfer. This architectural change directly benefits the integration and performance of the DeepSeekV2 model on Ascend, particularly when operating in graph mode. Additionally, the PR includes targeted improvements to the attention mechanism, Mixture-of-Experts (MoE) gating, and quantization processes specifically for the Ascend platform.

Highlights

  • Ascend KV Cache Separation: The KV cache management for Ascend NPUs has been fundamentally refactored to store Key and Value components in separate memory buffers. This separation aims to optimize memory access patterns and data transfer efficiency, particularly beneficial for disaggregated systems.
  • DeepSeekV2 Model Optimization for Ascend: DeepSeekV2 model support on Ascend has been significantly enhanced. This includes integrating the model with the Ascend attention backend and adapting its KV cache handling to leverage the newly separated Key and Value buffers, especially for graph mode execution.
  • Enhanced Ascend Attention Backend with Graph Mode Support: The Ascend attention backend now includes a dedicated forward_decode_graph path. This new function is designed to optimize attention calculations when running in graph mode, improving performance and better handling of RoPE (Rotary Positional Embeddings) within the KV cache.
  • MoE Gating Improvements on Ascend: Improvements have been made to the Mixture-of-Experts (MoE) gating mechanism on Ascend NPUs. The changes enable re-normalization of top-k weights, which can lead to more accurate and stable expert selection.
  • Quantization Process Refinements for Ascend: Adjustments have been made to the W8A8_INT8 quantization process for Ascend. These include refining the input offset data type and modifying parameters used in the NPU quantization function, contributing to more precise and efficient quantization.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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
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 introduces optimizations for Ascend hardware, including KV cache separation and graph mode support for DeepSeekV3 models. The changes are extensive and touch several parts of the system, from memory management to attention backends. My review identifies a critical issue in the torch_native_backend where arguments to scaled_dot_product_attention appear to be incorrect, a medium-severity issue regarding code duplication in the new Ascend attention logic, and a minor redundancy in an assertion. Overall, the changes are well-aligned with the PR's objectives, but the identified issues should be addressed.

@chenxu140 chenxu140 force-pushed the dev_fia branch 3 times, most recently from 6a63eaf to 0d9ba6b Compare August 20, 2025 03:06
@chenxu140 chenxu140 changed the title opt:ascend kv separation; dsv3 support graph Opt:ascend kv separation; dsv3 support graph; fused dequant+swiglu+quant Aug 20, 2025
@chenxu140 chenxu140 force-pushed the dev_fia branch 4 times, most recently from 748a37e to 08ae99f Compare August 20, 2025 08:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant