Skip to content
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

Specify upper bound on compute time #13

Open
caufieldjh opened this issue Jan 28, 2022 · 3 comments
Open

Specify upper bound on compute time #13

caufieldjh opened this issue Jan 28, 2022 · 3 comments

Comments

@caufieldjh
Copy link
Contributor

We don't want a NEAT job to take forever - it's expensive - so we will need some way to stop a job if it takes more than n hours.
This will need to be independent of the NEAT config so individual users don't just set it arbitrarily.

@caufieldjh
Copy link
Contributor Author

An area where templates may help (see https://cloud.google.com/compute/docs/instance-templates)

@justaddcoffee
Copy link

Discussing this again with @caufieldjh and @hrshdhgd - we will eventually want to set this limit to prevent very long GCP jobs

@caufieldjh
Copy link
Contributor Author

This could also be handled by the scheduler, as it's otherwise just sitting in a Jenkins pipeline waiting for a return from GCP

@caufieldjh caufieldjh transferred this issue from Knowledge-Graph-Hub/neat-ml Apr 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants