-
Notifications
You must be signed in to change notification settings - Fork 34
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
Ease of porting an existing project to rh #82
Comments
Hi Qasim! No, you don't need to modify those calls, because PyTorch modules and tensors should still be sent to devices within your program once the program is sent to remote hardware. The easiest way to get started with Runhouse is to take an existing Python function you'd like to run on remote hardware and sent it over through the rh.function(my_fn).to(my_hw) API. One example might be an inference function, like in this tutorial: https://runhouse-docs.readthedocs-hosted.com/en/latest/tutorials/examples/inference.html If you'd like to chat in more detail about your code and how to get started I'm happy to chat further. |
Super cool. I have an existing pytorch project that has over 100 .to(device) calls. is there an easy way to transform our codebase to incorporate runhouse? or should i manually change all my .to calls to accomodate for runhouse?
cc: @carolineechen @dongreenberg
The text was updated successfully, but these errors were encountered: