You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For best bulk transfer rates, it'd be great to control the HTTP/2 flow control window. Right now, I think we leave the defaults which are (IIRC) 64k per connection and 64k per stream. That means the server can't send a huge amount of data especially under a lot of concurrent streams. Also, we'll need to send a large number of WINDOW_UPDATE frames to up the flow control windows all the time.
Thank you to @Lukasa for reminding me that I want this when we were chatting about bulk H2 data transfer with AHC.
The text was updated successfully, but these errors were encountered:
For best bulk transfer rates, it'd be great to control the HTTP/2 flow control window. Right now, I think we leave the defaults which are (IIRC) 64k per connection and 64k per stream. That means the server can't send a huge amount of data especially under a lot of concurrent streams. Also, we'll need to send a large number of WINDOW_UPDATE frames to up the flow control windows all the time.
Thank you to @Lukasa for reminding me that I want this when we were chatting about bulk H2 data transfer with AHC.
The text was updated successfully, but these errors were encountered: