Balanced Pool
Open
Nobody has claimed this yet.
enhancement
Pool
- Dominant language
- JavaScript
- Stars
- 7.7k
- Forks
- 880
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 68
Description
One problem with the current pool implementation is that if a lot of requests gets dispatched at the same time, it assumes that all pipelines will have the same throughput, however that is not necessarily true and cause queue imbalance.
When all clients are busy, queue requests and listen to an event e.g. 'free' which indicates that a client is no longer busy.
Contributor guide
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 current pool implementation and tracing how requests are dispatched when all clients are busy. Define how queued requests should respond to a client's 'free' event, then verify that simultaneous requests remain balanced across pipelines with different throughput.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100