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

Open
#30 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
elixir
Domain
cloud, distributed-systems

Research direction

No files, tests, or entry points are named. Start by tracing how FLAME tracks concurrency and starts nodes, then determine where a configurable spinup_at_percentage belongs; done should include starting capacity before max_concurrency and behavior for unused capacity, with the intended scope clarified before implementation.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Elixir
Stars
1.2k
Forks
68
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from phoenixframework/flame

All issues in phoenixframework/flame

Similar issues

More Elixir issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.