superfly/corrosion

Use QUIC's congestion window size when sending data

Open

#61 opened on Sep 21, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (83 forks)auto 404
:detective: investigative workenhancementgood first issuehelp wanted

Repository metrics

Stars
 (1,817 stars)
PR merge metrics
 (PR metrics pending)

Description

During synchronization, a peer starts sending fairly large buffers (64KB at the time of this writing) and that can create congestion.

It might be faster to start w/ a buffer size equal to the congestion window size of the peer we're syncing with.

It would be better to respond to backpressure in a more appropriate way. Essentially every time a chunk is not fully written, then we've surpassed the congestion window size (which can be modified).

Contributor guide

Research direction
Investigate the current data sending implementation in the sync module. Find where the initial buffer size is set and how write operations handle partial writes. Research how to retrieve the QUIC peer's current congestion window size (e.g., via the QUIC library's API) and adjust the buffer size accordingly. Also consider how to properly respond to backpressure by pausing or resuming sends based on write readiness.
Tech stack
rust
Domain
backendnetworking
Issue type
Performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustQUICAsynchronous programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15