Performance Vision is now a part of Accedian

Learn More »
>>TCP Series #5: How to analyze TCP window problems (Video)

TCP Series #5: How to analyze TCP window problems (Video)

By |2018-04-07T17:53:16+00:00February 14th, 2018|Categories: Performance Troubleshooting|

Why should you care about TCP window problems and TCP windowing in general?

You should care about TCP window problems because they ultimately determine the speed of data transfers and hence the experience of your users accessing the applications. In this video, you will learn more about TCP windows in general, TCP Receive windows in particular and discover how they can impact performance.

A primer about TCP windows

According to Wikipedia,

The throughput of a communication is limited by two windows: the congestion window and the receive window. The congestion window tries not to exceed the capacity of the network (congestion control); the receive window tries not to exceed the capacity of the receiver to process data (flow control). The receiver may be overwhelmed by data if for example it is very busy (such as a Web server). Each TCP segment contains the current value of the receive window. If, for example, a sender receives an ack which acknowledges byte 4000 and specifies a receive window of 10000 (bytes), the sender will not send packets after byte 14000, even if the congestion window allows it.


About the Author:

Chris Greer
Chris is an independent network and application analyst, specializing in communications protocols. As the principal at Packet Pioneer, he regularly assists companies in tracking down the source of network and application performance problems using a variety of protocol analysis and monitoring tools including Wireshark. He also delivers training and develops technical content for several analysis vendors. (LinkedIn profile)