Consider using channels (e.g. tokio, futures, async-std) instead of SmallVec to pass messages
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Currently our InputStorage component uses a SmallVec to hold messages as they pass from one operation to another. This has been okay for performance, but it's possible that a channel-based approach could be superior. We should do some careful benchmarking and try out different message passing strategies to see what can achieve the best throughput.
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 InputStorage component and tracing how its SmallVec passes messages between operations. Build careful benchmarks comparing SmallVec with the mentioned channel-based strategies, including tokio, futures, and async-std. Done means the throughput results are clear and support a justified implementation choice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100