CS Enterprise // cloudshark.org

• Guest upload is turned off
• Log In

3 Capture Files

		File name	Packets	Size
		100MB_tcp_window_scale_disabled_client.pcapng	81123	6.8 MB
		100MB_tcp_window_scale_disabled_client_first_500_packets	499	43.9 KB
		100MB_tcp_window_scale_enabled_client.pcapng	79000	6.7 MB

Protocol choices made in older internet standards don’t scale to today’s network speeds. TCP ([Transmission Control Protocol](https://en.wikipedia.org/wiki/Transmission_Control_Protocol)) has been making networks go for a very, very long time. As with many of the early internet protocols, limitations that seemed reasonable then can have a negative effect on performance now. Protocol designers allowed for future options to augment existing fields in order to keep them working effectively into the future. Let’s take a closer look at TCP Window Size and the Window Scaling option to see how they can impact your network. You can read our [blog post of the full analysis here](https://enterprise.cloudshark.org/blog/tcp-window-scaling-examples).

Support: support@qacafe.com | Twitter: @cloudshark
CS Enterprise v3.15.0 ge05f57cb (CaaS-release)
© 2024 QA Cafe