Skip to content

[AutoDeploy] Investigate torch.export as a preprocessing step to InferenceOptimizer #4704

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

Open
lucaslie opened this issue May 27, 2025 · 0 comments
Assignees

Comments

@lucaslie
Copy link
Member

Currently, we run export on every rank

  • this can overload the CPU since every rank needs to run export on the CPU
  • May cause significant slow downs for long export time

To spin this a little further:

Everything until compile/cudagraph is very CPU heavy and broadly speaking the model is on the meta device and every rank performs the same set of computation. We may want to consider moving as much as we can into the pre-processing stage...

@lucaslie lucaslie self-assigned this May 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant