Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a section on flow control performance #3793

Merged
merged 6 commits into from
Jul 14, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions draft-ietf-quic-transport.md
Original file line number Diff line number Diff line change
Expand Up @@ -969,6 +969,19 @@ peer will be blocked for at least an entire round trip, and potentially for
longer if the peer chooses to not send STREAMS_BLOCKED frames.


## Flow Control Performance

An endpoint that is unable to ensure that a peer has flow control credit on the
order of the current BDP will have receive throughput limited by flow control.
Lost packets can cause gaps in the receive buffer, delaying the application
from consuming data and freeing up flow control window.

Sending timely updates of flow control limits can improve performance.
Sending packets only to provide flow control updates can increase network
load and adversely affect performance. Sending flow control updates along with
other frames, such as ACK frames, reduces the cost of those updates.


# Connections {#connections}

QUIC's connection establishment combines version negotiation with the
Expand Down