Pytorch qlinear #116
Merged
Pytorch qlinear #116
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
PanQiWei
approved these changes
May 30, 2023
|
So does this mean that before this PR, all quantisation was using Triton even with Or was this only the case for the new PEFT? Anyway, great work if it's adding more support for Windows users! |
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.
Changed to automatically switch to pytorch backend when trainable is enabled in cuda backend.
This trains at roughly 1.3x (70 minutes --> 90 minutes) slower pace than triton, but has the advantage of not using triton.