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.
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
torch.compile
compatibility withgenerate
+ static cache #29114torch.compile
compatibility withgenerate
+ static cache #29114Changes from 15 commits
6d669ee
4891050
724c694
0a00d6b
7472549
b214766
b9b627c
0c03b7d
28cdee0
190e0cf
5019e81
80b9072
a660486
2935462
5dbcef4
a8c4e10
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 am not sure it will ever be fixed!
If fixed, this will only be used in prepare inputs for generation, but my plan forward is to rely on the
cache_postiions
entirely, not the state of the cache to know the iteration we are at in the generate function! cc @ganteThere 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.
Use of
model_inputs
is indeed cleaner for me, as we only keep track of the cached_positions and increment them = no need for seen tokens!I'll let @gante validate it all, but LGTM
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.
we need to update
model_kwargs
withmodel_inputs["cache_position"]
, hence the additional argumentThere 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.
if we assume
use_cache
is used withcache_positions
(generate) then we probably don't need that anymore do we?Bit breaky but still
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.
@ArthurZucker Overall we should not assume
cache_positions
is an input to the model, e.g. for ONNX this would break thingsThere 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.
Why not? If we decide this to be the new format is it not better for ONNX as well?
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.
if the cache positions are given as input in the kwargs, and the length is 1, we can just increment it no ? (no arange that way)
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.
@ArthurZucker I left it that way because I don't properly understand the relationship between
position_ids
,cache_position
, especially for speculative decoding. Maybe it can be improved 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.
position_ids != cache_position if padding basically