-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Running multiple instances #27
Comments
Hi @maclandrol, Thank you! :) All spotty commands have the
And don't forget to stop all of them after :). I know that it's not very convenient, because you're basically copy-pasting the same configuration file several times, and then using the I faced this problem before as well, and I've made it slightly better it in the future version 1.2. The format of the configuration file will be a little bit different, and you will be able to specify there several instances. They will reuse the same S3 bucket. Also, scripts will be parameterizable, so you could use custom parameters: |
This answers all my question. Thanks ! I am using spotty inside a wrapper for automatic config generation and instance launching, so it should be fine. Reusing the same S3 bucket will be a really great feature. It might also be helpful to have a way to automatically stop the instance after a given time limit (I am using a scheduler now, which is working fine) ! |
Thank you for the feedback! I will add the time limit feature to my TODO list. |
Hello @apls777
Thanks for spotty, I love this project.
I was wondering if there is way to request several instances at the same time (like with sagemaker) to run the same code but with different configuration in parallel.
Also is it possible to pass arguments to
spotty run
like `spotty run train --config "path to file"``Thanks.
The text was updated successfully, but these errors were encountered: