oxidecomputer / oxidecomputer/crucible
Tune socket buffer size(s)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
tokio::net::TcpSocket offers both set_recv_buffer_size and set_send_buffer_size.
Tune these away from their defaults and investigate the impact on performance. This may also necessitate changing other things like the maximum number of in-flight jobs.
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
Locate the TcpSocket setup and the code controlling in-flight jobs, then establish a baseline for the current socket buffer defaults. Investigate performance across alternative receive and send buffer sizes and assess any effect on in-flight job limits. Done means the selected tuning and measured impact are documented and supported by the relevant performance evidence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100