Remove the queues between the stages
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Recently the queue sizes got changed to 1 from 1000, and the question came up why do we have queues at all?
Original Idea
The original idea was to create backpressure on the Stages, but in practice it just created a lot more objects in-memory while not actually reducing runtime.
New Idea
What if we removed the queues altogether and made it so that we only store declarative objects in the batcher that belongs to the stage.
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
The issue does not name any files, tests, or entry points. Start by locating the stage queue and batcher implementation, then compare the current queue-based flow with the proposed declarative-object approach. Done means queues are removed without losing stage backpressure or increasing runtime or in-memory object creation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100