TCP’s Initial Window—Deployment in the Wild and Its Impact on Performance

TCP congestion control and particularly its initial congestion window (IW) size is one long-debated topic that can influence Web performance. Its size is, however, assumed to be static by IETF recommendations-despite being network- and application-dependent-and only infrequently changed in its history. To understand if the standardization and research perspective still meets Internet reality, we study the IW configurations in IPv4 and of major content delivery networks (CDNs). We have been regularly inspecting IPv4 for HTTP and TLS servers to investigate their IW configuration and found a steady increase in IETF-recommended configurations. We additionally study how CDNs configure their IWs given their relevance for content distribution. To shed light on network-dependent CDN configurations, we use a globally distributed infrastructure of VPNs giving access to residential access links. We observe that most CDNs are well aware of the IW's impact and find a high amount of customization that is beyond current Internet standards. We find various initial window configurations, most below 50 segments, yet, with exceptions of up to 100 segments-the tenfold of current standards. This paper highlights that Internet reality has drifted away from recommended and standardized practices. Driven by these findings, we investigate the effects of this new reality on the slow start of Cubic and BBR congestion controlled TCP flows. We find that TCP pacing is a key to enable increased IWs when competing against other traffic.