Closed Bug 974932 Opened 10 years ago Closed 10 years ago
spdy: large upload chunk sizes, and fewer TLS application data records
TLS records are processed as atomic units.. so the bigger the unit the more latency added to the first byte (because the last byte needs to arrive too).. otoh there is framing overhead added to each record and significant CPU overhead too. So there is a tension between these two approaches. Obviously the download path needs to use small records and chunks in order to render in a streaming fashion and preserve priority. Both streaming and priority are less important on the upstream path. This patch does 3 things: 1] it uses a copy when necessary to coalesce the spdy frame header into the data frame - creating 1 TLS application record when there were 2 2] it increases our max spdy chunk size to 16000 from 4000. I think that's too big for the downstream path beacuse of the high degree of multiplexing and responsiveness we expect, but the tradeoff is right for the upstream path. 3] it sizes the buffer given to the input stream to a whole number of max data frames, preventing runts if the frames are filled all the way. This does not enforce max sized records, that really depends on whatever the nsIInputStream feeding HTTP does. Indeed I regularly see smallish ones come out of an upload to youtube test even with this patch - but the patch greatly reduces the total number of records. testing a youtube upload with this patch reduced the number of data records produced from 7700 to 1850... an optimal number would be around 1400. So it gets most of the way there.
I'm going to call this a feature and not a bug fix, and therefore only apply it to the leading edge of spdy (3.1 and http/2)
Assignee: nobody → mcmanus
Status: NEW → ASSIGNED
Comment on attachment 8379032 [details] [diff] [review] spdy large upload chunk sizes, and fewer TLS application data records Review of attachment 8379032 [details] [diff] [review]: ----------------------------------------------------------------- ::: netwerk/protocol/http/SpdyStream31.cpp @@ +699,5 @@ > // This function calls mSegmentReader->OnReadSegment to report the actual SPDY > // bytes through to the SpdySession31 and then the HttpConnection which calls > // the socket write function. It will accept all of the inline and stream > // data because of the above 'commitment' even if it has to buffer > + nit: whitespace
Attachment #8379032 - Flags: review?(hurley) → review+
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
You need to log in before you can comment on or make changes to this bug.