Closed
Bug 1851908
Opened 1 year ago
Closed 1 year ago
Add a preference to specify neqo's congestion control algorithm
Categories
(Core :: Networking: HTTP, enhancement, P3)
Tracking
()
RESOLVED
FIXED
119 Branch
| Tracking | Status | |
|---|---|---|
| firefox119 | --- | fixed |
People
(Reporter: acreskey, Assigned: acreskey)
References
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
Currently we configure Neqo to use the cubic congestion control algorithm.
It would be used to be able to specify the algorithm choice (currently we also support NewReno) via pref.
|
Assignee | |
Comment 1•1 year ago
|
||
We want to experiment with NewReno so expose this via pref.
Pushed by acreskey@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/25b4a7559a80
Add a preference to specify neqo's congestion control algorithm r=necko-reviewers,kershaw
|
||
Comment 3•1 year ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox119:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 119 Branch
|
|
Assignee | |
Comment 4•1 year ago
|
||
This is exposed as the pref,
network.http.http3.cc_algorithm
# 0 => NewReno
# 1 => Cubic (default)
You need to log in
before you can comment on or make changes to this bug.
Description
•