You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@trafficserver.apache.org by GitBox <gi...@apache.org> on 2022/09/12 23:43:16 UTC
[GitHub] [trafficserver] shinrich commented on pull request #9085: Make HTTP/2 session and stream windows configurable
shinrich commented on PR #9085:
URL: https://github.com/apache/trafficserver/pull/9085#issuecomment-1244716790
Hmm. I'd be open to a solution that dynamically changes the initial window size based on the number of open streams. I would be concerned that fiddling the setting that frequently would mess up the the peer.
One benefit of having two district settings is if there are in fact numerous concurrent streams, it is unlikely that one will suck up all the resources before the other streams can get started.
Without this PR or some sort of dynamically resizing stream window in setting, we do need to update our documentation to tell folks that they should set the connection window size to be number of expected concurrent active streams * the actual desired window size.
I noticed this issue primarily with session resource with H2 to origin. It probably doesn't matter as much for the client side. But on the origin side, you are more vulnerable to greedy streams.
--
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: github-unsubscribe@trafficserver.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org