workaround issue with weights loading in 8bit in optimum notebooks #1575
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
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
eaidova
force-pushed
the
ea/pin_optimum
branch
from
daec5e5 to
37bf611
Compare
eaidova
force-pushed
the
ea/pin_optimum
branch
from
37bf611 to
ffd83bc
Compare
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.
in some notebooks we can see that models load in 8bit by default that may be incompatible with expected flow in notebook (e.g. notebook demonstrates quantization or weights compression in int4), but flag load_in_8bit=False is broken in optimum-intel if used OVModelForXXX class with export=True.
Fix: huggingface/optimum-intel#495
this is workaround until fix will not be merged