[cubic/cuback] optionally use alpha=1 after loss - #688
Open
kazuho wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
quicly_context_t::cubic_loss_alpha_onecwnd_priorSimulation results
Each point below contains 60 paired runs, with the same randomized flow starts for stock, alpha-one, and Pico. Each run used a 10-second warmup followed by a 30-second measurement interval. Pacing and Rapid Start were enabled, ECN was disabled, and bottleneck utilization was approximately 100%.
Values are the tested flow's mean bottleneck share, with per-run SD in parentheses.
Against one stock Cubic contender
Fair share is 50%.
Paired alpha-one minus stock differences, with 95% confidence intervals:
Against three stock Cubic contenders
Fair share is 25%.
Paired alpha-one minus stock differences, with 95% confidence intervals:
In the three-contender experiment, alpha-one closed 62% to 76% of the stock-to-Pico share gap. The BDP20 Cuback runs were almost entirely Reno-friendly: stock recorded four non-friendly/crossover updates in total, and alpha-one recorded one. The lower-end bandwidth distributions were unimodal, without steep secondary peaks.
The heavily congested profile was excluded from the roofline tables because it was predominantly Cubic-controlled and Pico was less aggressive than Cubic there.
Tests
cmake --build build/default -j2build/default/test.t