Create a new tensor arg for stride_per_key_per_rank to facilitate torch.export #2950
Conversation
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
facebook-github-bot
added
the
CLA Signed
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D74207283 |
…s for VBE KJTs. (meta-pytorch#2949) Summary: Update the `_maybe_compute_stride_kjt` logic to calculate stride based off of `inverse_indices` for VBE KJTs. Currently, stride of VBE KJT with `stride_per_key_per_rank` is calculated as the max "stride per key". This is different from the batch size of the EBC output KeyedTensor which is based off of inverse_indices. This causes issues in IR module serialization: debug doc. Differential Revision: D74273083
…ch.export (meta-pytorch#2950) Summary: # Context * Currently torchrec IR serializer can't handle variable batch KJT use case. * To support VBE KJT, the `stride_per_key_per_rank` field needs to be flattened as a variable in the pytree flatten spec for a VBE KJT to be unflattened correctly by`torch.export`. * Currently `stride_per_key_per_rank` is a List. To flatten the `stride_per_key_per_rank` info as a variable we have to add a new tensor field for it. # Ref Differential Revision: D74207283
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D74207283 |
jd7-tr
added a commit
to jd7-tr/torchrec
that referenced
this pull request
May 7, 2025
…ch.export (meta-pytorch#2950) Summary: # Context * Currently torchrec IR serializer can't handle variable batch KJT use case. * To support VBE KJT, the `stride_per_key_per_rank` field needs to be flattened as a variable in the pytree flatten spec for a VBE KJT to be unflattened correctly by`torch.export`. * Currently `stride_per_key_per_rank` is a List. To flatten the `stride_per_key_per_rank` info as a variable we have to add a new tensor field for it. # Ref Differential Revision: D74207283
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary:
Context
stride_per_key_per_rankfield needs to be flattened as a variable in the pytree flatten spec for a VBE KJT to be unflattened correctly by`torch.export.stride_per_key_per_rankis a List. To flatten thestride_per_key_per_rankinfo as a variable we have to add a new tensor field for it.Ref
Differential Revision: D74207283