for careful resume, use max(latest, smoothed) rather than smoothed #580
Conversation
This file contains 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
…s smoothed can be a 1/2 than the latest ack rate during slow start
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.
Generally speaking, smoothed is better, but it can be 1/2 of the latest during slow start. Considering the number of connections that never exit slow start, it would be better to use
max(smoothed, latest)as the jumpstart cwnd.Note that
latestbeing reported covers a window of 50ms (see QUICLY_DELIVERY_SAMPLE_PERIOD andquicly_ratemeter_report), hopefully that is enough to hide the effect of ACKs arriving sporadically.