-
Couldn't load subscription status.
- Fork 6.5k
[bitsandbytes] improve dtype mismatch handling for bnb + lora. #11270
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
Merged
Merged
Changes from 7 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
5801679
improve dtype mismatch handling for bnb + lora.
sayakpaul 8bf12e8
add a test
sayakpaul 40958f7
Merge branch 'main' into improve-dtype-mismatch-bnb-lora
sayakpaul 58c8183
Merge branch 'main' into improve-dtype-mismatch-bnb-lora
sayakpaul 44e4ded
Merge branch 'main' into improve-dtype-mismatch-bnb-lora
sayakpaul fd694b0
Merge branch 'main' into improve-dtype-mismatch-bnb-lora
sayakpaul 2107d4c
Merge branch 'main' into improve-dtype-mismatch-bnb-lora
sayakpaul 8b7ef9c
fix and updates
sayakpaul 40c0d89
Merge branch 'main' into improve-dtype-mismatch-bnb-lora
sayakpaul fccff45
update
sayakpaul 98d84f9
Merge branch 'main' into improve-dtype-mismatch-bnb-lora
sayakpaul File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
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.
since we specified dtype = model.dtype in the
dequantize_bnb_weight, won't themodule_weightshave the same dtype as model ?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.
Yes it will. But the LoRA params would not be in that dtype as they are derived early from the module_weight data dtype. This is why in the error trace, the error happens in
peft.Uh oh!
There was an error while loading. Please reload this page.
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.
To summarize, we have the following right ? :
-> dtype mismatch issue due to loras param not having the same dtype as module_weight
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.
Yeah. We don't really have any special treatment to handle LoRA param dtype. Ccing @BenjaminBossan here.
Well, we use the quant_state:
diffusers/src/diffusers/quantizers/bitsandbytes/utils.py
Line 173 in ea5a6a8
But then we also perform another type-casting:
diffusers/src/diffusers/quantizers/bitsandbytes/utils.py
Line 189 in ea5a6a8
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.
Just to clarify: This is unrelated to the LoRA parameters. Instead, what happens is that a PEFT
LoraLayerwraps the base layer and callsself.base_layer(x), which should just be the result from the original layer. Due to the change in dtype, we will encounter the dtype mismatch there.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.
This works though.
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.
Yeah, it happens inside the LoRA layer, but what I mean is that the LoRA weights are not involved, it's the call to the base layer that is causing the issue.