commit | 9e75db181609abbe2120ff918ca8b5611c757efe | [log] [tgz] |
---|---|---|
author | QUICHE team <quiche-dev@google.com> | Tue Apr 02 17:21:31 2019 -0400 |
committer | Victor Vasiliev <vasilvv@google.com> | Wed Apr 03 00:09:25 2019 +0000 |
tree | c6e529db5862ed93f337c2a84bc58ff010db0380 | |
parent | f41bf64c347693484d5ffeab03fd85674bb0f2a7 [diff] |
Set QUIC's max packet size to whatever Quartc configures. Currently, Quartc only configures the max packet size on the packet writer. However, the QuicConnection keeps its own, separate max packet size. This is set from a constant in quic_constants.h (kDefaultMaxPacketSize = 1350 for clients or kDefaultServerMaxPacketSize = 1000 for servers). Calling QuicConnection::SetMaxPacketLength() updates the connection's value to match the packet writer's value. The effect can be confirmed by running Quartc tests. Before this change, we saw 1000 bytes as the max packet size on the server: Packet size stats=[mean = 349, stddev = 394, min = 19, max = 1000, 25% = 36, 50% = 130, 75% = 787, 90% = 1000] After this change, we observe 1200 bytes as the max packet size in both directions: Packet size stats=[mean = 262, stddev = 432, min = 19, max = 1200, 25% = 29, 50% = 35, 75% = 141, 90% = 1200] gfe-relnote: n/a (Quartc only) PiperOrigin-RevId: 241603141 Change-Id: I9da1c0dcfa37af22c2f0decdf27f9081eec22444
QUICHE (QUIC, Http/2, Etc) is Google‘s implementation of QUIC and related protocols. It powers Chromium as well as Google’s QUIC servers and some other projects.
The code is currently in process of being moved from https://cs.chromium.org/chromium/src/net/third_party/ into this repository. Please excuse our appearance while we're under construction.