[performance] Use buffers instead of channels
- Dominant language
- Rust
- Stars
- 40
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Use buffers instead of channels, maybe https://crates.io/crates/crossbeam could help or we can impl a channel like (to be easier to use) which has a fixed buffer where it keeps data and tx sends offsets and rx exposes slices based on those offsets, as we only need to access the buffer for reading in rx
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by locating the channel, tx, and rx usage in the Rust implementation, then compare the existing data flow with crossbeam's buffering model. Done would require an agreed buffer design and evidence that it improves performance without changing the transport behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100