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

Hot start a new node when a percentage of max_concurrency is reached #30

Open
DeemoONeill opened this issue Apr 19, 2024 · 1 comment
Open

Comments

@DeemoONeill
Copy link

Currently FLAME will only start a new node when the maximum concurrency is reached which can lead to cold starts during heavy load.

Adding a new parameter for "spinup_at_percentage" and being able to pass in something like 0.8. So that a new node starts at 80% capacity to pre-empt load.

These could have an aggressive idle timer so they stop if that capacity isn't used.

Eventually perhaps monitoring the rate of incoming work so that new nodes are spun up if it can't cope.

@DeemoONeill
Copy link
Author

I've done an initial implementation in #32 There might be some issues around the new runner becoming the min_runner by default. And balancing load across all of the runners.

a possible way to address that would be to only add a new runner if the current capacity across all runners exceeds the threshold, rather than just the capacity on the min_runner. That would require more extensive changes.

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

1 participant