-
Notifications
You must be signed in to change notification settings - Fork 563
Fix TorchRec inference solution with updated torch.fx + TorchScript Solution #2101
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
@PaulZhang12 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
…olution (#2101) Summary: Previously, the TorchRec inference solution used torch.deploy, which isn't supported, and the solution itself was outdated and broken. This PR revamps the inference example with Torch.FX and TorchScript, which more accurately represents what is used in production for RecSys currently. Furthermore, the example was constructed with simplicity as the top priority, with fewer package requirements and steps to run. This is the first iteration of the inference example, with more to come! Pull Request resolved: #2101 Differential Revision: D58478461 Pulled By: PaulZhang12
This pull request was exported from Phabricator. Differential Revision: D58478461 |
31c9668
to
6377138
Compare
…olution (#2101) Summary: Previously, the TorchRec inference solution used torch.deploy, which isn't supported, and the solution itself was outdated and broken. This PR revamps the inference example with Torch.FX and TorchScript, which more accurately represents what is used in production for RecSys currently. Furthermore, the example was constructed with simplicity as the top priority, with fewer package requirements and steps to run. This is the first iteration of the inference example, with more to come! Pull Request resolved: #2101 Differential Revision: D58478461 Pulled By: PaulZhang12
6377138
to
a335953
Compare
This pull request was exported from Phabricator. Differential Revision: D58478461 |
1 similar comment
This pull request was exported from Phabricator. Differential Revision: D58478461 |
…olution (#2101) Summary: Previously, the TorchRec inference solution used torch.deploy, which isn't supported, and the solution itself was outdated and broken. This PR revamps the inference example with Torch.FX and TorchScript, which more accurately represents what is used in production for RecSys currently. Furthermore, the example was constructed with simplicity as the top priority, with fewer package requirements and steps to run. This is the first iteration of the inference example, with more to come! Pull Request resolved: #2101 Differential Revision: D58478461 Pulled By: PaulZhang12
a335953
to
10cd168
Compare
…olution (#2101) Summary: Previously, the TorchRec inference solution used torch.deploy, which isn't supported, and the solution itself was outdated and broken. This PR revamps the inference example with Torch.FX and TorchScript, which more accurately represents what is used in production for RecSys currently. Furthermore, the example was constructed with simplicity as the top priority, with fewer package requirements and steps to run. This is the first iteration of the inference example, with more to come! Pull Request resolved: #2101 Differential Revision: D58478461 Pulled By: PaulZhang12
This pull request was exported from Phabricator. Differential Revision: D58478461 |
10cd168
to
eec5df3
Compare
Previously, the TorchRec inference solution used torch.deploy, which isn't supported, and the solution itself was outdated and broken. This PR revamps the inference example with Torch.FX and TorchScript, which more accurately represents what is used in production for RecSys currently. Furthermore, the example was constructed with simplicity as the top priority, with fewer package requirements and steps to run. This is the first iteration of the inference example, with more to come!