TimelyDataflow / TimelyDataflow/timely-dataflow
Communication design: MergeQueues
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 293
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 4
Description
@frankmcsherry what's the reasoning behind having the MergeQueue merge contiguous Bytes? Where do you expect performance benefits from this? /cc @LorenzoMartini @antiguru
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 locating the MergeQueue implementation and tracing how contiguous Bytes are merged. Read the surrounding communication-design context and determine which performance benefit is expected. Done would require a clear, agreed rationale or a concrete follow-up change, but the issue currently asks only an unanswered design question.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100