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.

Sign up for GitHub

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

Jump to bottom

Rely on API error messages instead of checking #5

Open
gullmar opened this issue Oct 11, 2024 · 0 comments
Open

Rely on API error messages instead of checking #5

gullmar opened this issue Oct 11, 2024 · 0 comments
Labels
optimization/refactoring Should reduce the resources this consumes or make it easier to maintain

Comments

@gullmar
Copy link
Collaborator

gullmar commented Oct 11, 2024

Instead of checking for available memory and jobs in advance, the orchestrator should always try to start a run, catch possible errors, and maybe wait for a cooldown period when a run fails to start.

This behavior would result in less API calls.
@gullmar gullmar added the optimization/refactoring Should reduce the resources this consumes or make it easier to maintain label Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
optimization/refactoring Should reduce the resources this consumes or make it easier to maintain
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gullmar