perf(quic): BBR congestion control

Open
#47 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
c

Research direction

The payload names no source files, only the CUBIC implementation and the test_h3c simulator. Start by finding where the existing CUBIC congestion controller is wired into the QUIC sender and how test_h3c selects its loss and latency profiles. Design a pluggable interface first, since BBRv2/v3 depends on it. Done means BBR variants run under those profiles with measured throughput compared against CUBIC. Ask the maintainers for the interface design before coding.

Written by the indexing model from the issue text.

Description

enhancement P2: later

Only CUBIC (RFC 9438) is implemented. BBR does better on lossy, high-bandwidth-delay links. Make congestion control pluggable and add BBRv2/v3, and measure both under the test_h3c simulator's loss and latency profiles.

Dominant language
C
Stars
0
Forks
0
Avg merge
20h 4m
Merged PRs (30d)
25

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from public/cursed-http

All issues in public/cursed-http

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.