liquidmetal-dev / liquidmetal-dev/battery
Pool autoscaling policies (min/max, demand-based)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- Avg merge
- 2h 13m
- Merged PRs (30d)
- 33
Description
Pools currently reconcile toward a fixed target size. Add support for autoscaling policies on top of the existing per-pool reconciler:
- Min/max bounds on pool size
- Demand-based scaling, e.g. grow the pool when claim rate or claim latency crosses a configurable threshold, and shrink back down when demand drops
This builds on the existing reconciler/PoolManager lifecycle work and should fit into the per-pool spec rather than requiring a new subsystem.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing per-pool reconciler and PoolManager lifecycle work. Define how autoscaling policies fit into the per-pool spec, including min/max bounds, configurable claim-rate or claim-latency thresholds, and scale-down behavior. Done means pools can reconcile dynamically within their configured bounds as demand changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100