capsule-rs / capsule-rs/capsule
need a means where we can specify the batch size for transmit
Open
enhancement
- Dominant language
- Rust
- Stars
- 443
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
it is currently hardcoded to 32 but that’s too large for some very low latency apps and would be nice if this was tunable. I can create a PR if needed
Contributor guide
Research direction
The issue does not name a file, test, or entry point; start by locating the hardcoded batch size of 32 in the transmit path and tracing how transmission configuration is exposed. Done means the batch size can be tuned for low-latency applications without changing the default behavior, with the existing project checks passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100