Add GPTQModel support for evaluating GPTQ models #2217
Conversation
This file contains 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
Qubitium
requested review from
haileyschoelkopf and
lintangsutawika
as code owners
|
|
|
@baberabb Hi, can we get some action on this? What do we need to do to get this reviewed and merged? |
|
@baberabb Ruff/Lint checks passed. Awaiting review. Thanks. |
|
@baberabb Ping. Please check our PR. We will push a unit test into |
Qubitium
changed the title
|
@baberabb Unit test added. |
|
Hi! Thanks for the PR, and sorry it took ages for us to review. This looks good to me, but I want to run it through @haileyschoelkopf as well. ps. 3.8 test failing because of a recent |
baberabb
approved these changes
Oct 25, 2024
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.
Add option to use GPTQModel for
lm_eval. GPTQModel is a replacement for AutoGPTQ on GPTQ quantization and inference with better model support and much faster inference speed out-of-the-box. We have been using it internally with lm-eval for months without issue.