-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
[Bugfix][Benchmark] Fix Marlin benchmark #19929
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
Conversation
👋 Hi! Thank you for contributing to the vLLM project. 💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels. Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging. To run CI, PR reviewers can either: Add 🚀 |
There was a problem hiding this 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 @22quinn, 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 focuses on enhancing the benchmark_marlin.py
script. My primary goal was to fix the existing benchmark, which had become outdated due to recent updates in Marlin operations. Additionally, I've expanded its capabilities to test a broader range of quantization data types, including FP4 and FP8, ensuring a more robust and relevant performance assessment for Marlin kernels.
Highlights
- Benchmark Script Fixes: I've updated the
benchmark_marlin.py
script to align with recent changes in Marlin operations, addressing a bug that caused the previous benchmark to break. This ensures the benchmark accurately reflects the current state of Marlin performance. - Expanded Quantization Type Coverage: The benchmark now includes support for additional quantization data types, specifically
float4_e2m1f
(FP4) andfloat8_e4m3fn
(FP8). This provides a more comprehensive performance evaluation across various quantization schemes. - Improved Quantization Logic Handling: I've refined the
bench_run
function to correctly handle different Marlin quantization scenarios, including those with zero-points (uint4
,uint8
), varying group sizes, and activation order. This involves conditional execution paths for different quantization methods (e.g., AWQ Marlin, Marlin_24, GPTQ repack) and updated function signatures forgptq_marlin_gemm
.
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 is currently in preview and 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 to provide feedback.
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
-
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. ↩
There was a problem hiding this 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 fixes and extends the Marlin benchmark script by addressing outdated logic and expanding test coverage to include FP4, FP8, and AWQ-style quantization. The changes ensure that only supported configurations are benchmarked. I've provided suggestions to improve code clarity and reduce redundancy. Overall, this is a solid contribution.
) | ||
|
||
marlin_zp = torch.empty(0, dtype=torch.int, device=b.device) | ||
marlin_24_w_ref = None |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: shall we just move this to a dedicated function to improve the code readability?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
refactored a bit
Will wait for @mgoin to take a look |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really appreciate this, thanks
Signed-off-by: Will Eaton <weaton@redhat.com>
Essential Elements of an Effective PR Description Checklist
supported_models.md
andexamples
for a new model.Purpose
benchmark_marlin.py
is outdated. A few updates to the marlin ops have been introduced, breaking the benchmark script. This PR fix the benchmark and also expands it to test more quantization data types.Fix #19909
Test Plan
Test Result
(Optional) Documentation Update