-
Notifications
You must be signed in to change notification settings - Fork 523
Enable TW pruning, no remapping #2343
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
Conversation
This pull request was exported from Phabricator. Differential Revision: D61879687 |
This pull request was exported from Phabricator. Differential Revision: D61879687 |
…ows post pruning (pytorch#2343) Summary: Pull Request resolved: pytorch#2343 Enable TW pruning for TorchRec inference modules. We switch from pruned_indices_remapping to num_rows_post_pruning given the fact that the indices remapping isn't calculated until after physical transformations. Logical transformations (optimizing the model itself) should not depend on the reset of physical transformations, and the actual index remapping will be set later on in model loading Differential Revision: D61879687
7deaaac
to
33c4a4f
Compare
This pull request was exported from Phabricator. Differential Revision: D61879687 |
…ows post pruning (pytorch#2343) Summary: Pull Request resolved: pytorch#2343 Enable TW pruning for TorchRec inference modules. We switch from pruned_indices_remapping to num_rows_post_pruning given the fact that the indices remapping isn't calculated until after physical transformations. Logical transformations (optimizing the model itself) should not depend on the reset of physical transformations, and the actual index remapping will be set later on in model loading Reviewed By: dstaay-fb Differential Revision: D61879687
33c4a4f
to
89f75ee
Compare
This pull request was exported from Phabricator. Differential Revision: D61879687 |
…ows post pruning (pytorch#2343) Summary: Pull Request resolved: pytorch#2343 Enable TW pruning for TorchRec inference modules. We switch from pruned_indices_remapping to num_rows_post_pruning given the fact that the indices remapping isn't calculated until after physical transformations. Logical transformations (optimizing the model itself) should not depend on the reset of physical transformations, and the actual index remapping will be set later on in model loading Reviewed By: dstaay-fb Differential Revision: D61879687
89f75ee
to
1c73501
Compare
This pull request was exported from Phabricator. Differential Revision: D61879687 |
…ows post pruning (pytorch#2343) Summary: Pull Request resolved: pytorch#2343 Enable TW pruning for TorchRec inference modules. We switch from pruned_indices_remapping to num_rows_post_pruning given the fact that the indices remapping isn't calculated until after physical transformations. Logical transformations (optimizing the model itself) should not depend on the reset of physical transformations, and the actual index remapping will be set later on in model loading Reviewed By: dstaay-fb Differential Revision: D61879687
1c73501
to
f7b8ef9
Compare
…ows post pruning (pytorch#2343) Summary: Pull Request resolved: pytorch#2343 Enable TW pruning for TorchRec inference modules. We switch from pruned_indices_remapping to num_rows_post_pruning given the fact that the indices remapping isn't calculated until after physical transformations. Logical transformations (optimizing the model itself) should not depend on the reset of physical transformations, and the actual index remapping will be set later on in model loading Reviewed By: dstaay-fb Differential Revision: D61879687
This pull request was exported from Phabricator. Differential Revision: D61879687 |
f7b8ef9
to
f83d35b
Compare
…ows post pruning (pytorch#2343) Summary: Pull Request resolved: pytorch#2343 Enable TW pruning for TorchRec inference modules. We switch from pruned_indices_remapping to num_rows_post_pruning given the fact that the indices remapping isn't calculated until after physical transformations. Logical transformations (optimizing the model itself) should not depend on the reset of physical transformations, and the actual index remapping will be set later on in model loading Differential Revision: D61879687 Reviewed By: dstaay-fb
Summary: Enable TW pruning for TorchRec inference modules. We switch from pruned_indices_remapping to num_rows_post_pruning given the fact that the indices remapping isn't calculated until after physical transformations. Logical transformations (optimizing the model itself) should not depend on the reset of physical transformations, and the actual index remapping will be set later on in model loading
Differential Revision: D61879687