Skip to content

Comments

[4/n]decouple quantization implementation from vLLM dependency#9191

Merged
zhyncs merged 7 commits intosgl-project:mainfrom
Hongbosherlock:remove_vllm
Aug 14, 2025
Merged

[4/n]decouple quantization implementation from vLLM dependency#9191
zhyncs merged 7 commits intosgl-project:mainfrom
Hongbosherlock:remove_vllm

Conversation

@Hongbosherlock
Copy link
Contributor

Motivation

follow #8112
remove vllm dependency for AWQ and GPTQ quantization.

co-author:@AniZpZ

Modifications

Accuracy Tests

Benchmarking and Profiling

Checklist

Co-authored-by: AniZpZ <aniz1905@gmail.com>
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 @Hongbosherlock, 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, part of a series, aims to decouple the AWQ and GPTQ quantization implementations from a direct dependency on vLLM. By refactoring the import paths for specific quantization kernels, it allows SGLang to manage these quantization methods independently, improving modularity and reducing external dependencies.

Highlights

  • Decoupled Quantization Methods: Removed AWQ and GPTQ related configurations from the VLLM_QUANTIZATION_METHODS list, signifying their independence from vLLM.
  • Direct Kernel Imports: Replaced imports of quantization operations from vllm._custom_ops with direct imports of corresponding kernels (e.g., awq_marlin_repack, gptq_gemm) from sgl_kernel.
  • Streamlined GPTQ Method Handling: Eliminated the gptq_get_quant_method function and associated monkey patching, simplifying how GPTQ quantization methods are applied.
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.

@gemini-code-assist
Copy link
Contributor

Warning

Gemini encountered an error creating the review. You can try again by commenting /gemini review.

@Hongbosherlock
Copy link
Contributor Author

The CI seems to still be using sgl-kernel==0.3.4.post1 instead of 0.3.5.

@zhyncs zhyncs merged commit 2cc9eea into sgl-project:main Aug 14, 2025
66 of 90 checks passed
@AniZpZ AniZpZ mentioned this pull request Aug 15, 2025
15 tasks
@Hongbosherlock Hongbosherlock deleted the remove_vllm branch August 15, 2025 02:37
narutolhy pushed a commit to narutolhy/sglang that referenced this pull request Aug 17, 2025
…roject#9191)

Co-authored-by: AniZpZ <aniz1905@gmail.com>
Co-authored-by: Yineng Zhang <me@zhyncs.com>
MahmoudAshraf97 pushed a commit to MahmoudAshraf97/sglang that referenced this pull request Sep 8, 2025
…roject#9191)

Co-authored-by: AniZpZ <aniz1905@gmail.com>
Co-authored-by: Yineng Zhang <me@zhyncs.com>
TestFile("test_gguf.py", 96),
TestFile("test_gptqmodel_dynamic.py", 102),
TestFile("test_vllm_dependency.py", 185),
# TestFile("test_gguf.py", 96),
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we add gguf support back?
cc @AniZpZ @Hongbosherlock ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

we'll work on it

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.

3 participants