Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Why do TCP conversations constantly refresh?

I want to diagnose TCP throughput of large video file uploads. The TCP throughput graph provides a good view which I use to visualize an issue during the transfer. The transfer is divided into many (50MB~20MB) chunks, so I use the TCP Conversation view to find the ones I want to graph. I locate these easily because they show up as many 443 transfers > 18MB. Of course the .pcap is large (600 MB), even using truncated frames, so the Conversation view takes a while to populate, which is expected and ok if it only did it once :)

The problem occurs when I want to show the throughput graph. First I select the conversation I want and then use the graph button. But rather than graph the selected conversation, it chooses the first stream (BUG #1?).

When the graph opens, it also reload the TCP Conversation chart which again takes a long time (BUG #2?)

In order to use the TCP Conversation chart I need the stream ID, which would be helpful if it was listed as a column in the TCP conversation view (REQUEST #1). But instead I use the Follow the Stream button and close it quickly. However this again loads the TCP Conversation which takes a long time (BUG #1 again).

Is there a better/faster way to display TCP throughput charts of the TCP conversations I'm interested in? Or maybe a better, more detailed tool/way, that helps me understand congestion control?

Thanks, Paul

Why do TCP conversations constantly refresh?

I want to diagnose TCP throughput of large video file uploads. The TCP throughput graph provides a good view which I use to visualize an issue during the transfer. The transfer is divided into many (50MB~20MB) chunks, so I use the TCP Conversation view to find the ones I want to graph. I locate these easily because they show up as many 443 transfers > 18MB. Of course the .pcap is large (600 MB), even using truncated frames, so the Conversation view takes a while to populate, which is expected and ok if it only did it once :)

The problem occurs when I want to show the throughput graph. First I select the conversation I want and then use the graph button. But rather than graph the selected conversation, it chooses the first stream (BUG #1?).

When the graph opens, it also reload the TCP Conversation chart which again takes a long time (BUG #2?)

In order to use the TCP Conversation chart I need the stream ID, which would be helpful if it was listed as a column in the TCP conversation view (REQUEST #1). But instead I use the Follow the Stream button and close it quickly. However this again loads the TCP Conversation which takes a long time (BUG #1 again).

Is there a better/faster way to display TCP throughput charts of the TCP conversations I'm interested in? Or maybe a better, more detailed tool/way, that helps me understand congestion control?

Thanks, Paul