maskit commented on issue #8199:
URL: https://github.com/apache/trafficserver/issues/8199#issuecomment-907940746
> If the stream and session are set to the same value, each stream will push
through until it finishes or exhausts the stream (and session) window.
This makes perfect sense if there's only one stream on a connection, right?
Needless to say, a connection should be fully utilized regardless of the number
of streams on the session.
I think what we should do is updating stream window size when the number of
streams changes. More specifically, we should adjust stream window sizes to
`connection-window-size / #-of-active-streams`. Below is from RFC 7430:
>In addition to changing the flow-control window for streams that are
not yet active, a SETTINGS frame can alter the initial flow-control
window size for streams with active flow-control windows (that is,
streams in the "open" or "half-closed (remote)" state). When the
value of SETTINGS_INITIAL_WINDOW_SIZE changes, a receiver MUST adjust
the size of all stream flow-control windows that it maintains by the
difference between the new value and the old value.
Sending a SETTING frame mentioned above automatically maintains the best
window sizes for streams. You can simply set the max window size you want to
allow for an H2 connection to the existing
`proxy.config.http2.initial_window_size_in`.
What size are you going to recommend for initial window size for streams if
we have the setting for connections that you suggested? You may be able to set
`session_window_multiplier_in` based on an expected average number of streams
on a connection, but that fully utilize a connection only if a connection has
the expected number of streams. I don't think that is great where we can adjust
it dynamically.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
