Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

argue why the slow transfer is slow

Hello Friends, My task is to find out why one trace is slow.

https://drive.google.com/open?id=1DBQP_OxUxnp45uaHa0REbK4znupVs0oT --->slow https://drive.google.com/open?id=1w__DGZUtosFEC1AKaYBZjRSvjeJa5phZ --->fast

Both the capture is made near the server via TAPs.

From my findings the slow transfer is slow because of the nature of the application. The application sends some data to sever and the server only answers after resumption of this application data. Both the traces have the same pattern of packet flow in the sense that the server waits still the client sends some data. As the RTT of the slow transfer is high the total duration is longer. Can anyone find some other reason for this?

I could calculate the slow transfer took 12 seconds as there are 253 packets send by the client which took the time equal or grater than to RTT which is 2530ms. There are 2 packets sent after the re transmission time out which is took 3041 ms. Thus the network time spend by the slow transfer is 5571ms. The time which the server took till the capture point is not taken into account. Did i miss something?

argue why the slow transfer is slow

Hello Friends, My task is to find out why one trace is slow.

https://drive.google.com/open?id=1DBQP_OxUxnp45uaHa0REbK4znupVs0oT --->slow https://drive.google.com/open?id=1w__DGZUtosFEC1AKaYBZjRSvjeJa5phZ --->fastslow --> https://drive.google.com/open?id=1w__DGZUtosFEC1AKaYBZjRSvjeJa5phZ fast ---> https://drive.google.com/open?id=1DBQP_OxUxnp45uaHa0REbK4znupVs0oT

Both the capture is made near the server via TAPs.

From my findings the slow transfer is slow because of the nature of the application. The application sends some data to sever and the server only answers after resumption of this application data. Both the traces have the same pattern of packet flow in the sense that the server waits still the client sends some data. As the RTT of the slow transfer is high the total duration is longer. Can anyone find some other reason for this?

I could calculate the slow transfer took 12 seconds as there are 253 packets send by the client which took the time equal or grater than to RTT which is 2530ms. There are 2 packets sent after the re transmission time out which is took 3041 ms. Thus the network time spend by the slow transfer is 5571ms. The time which the server took till the capture point is not taken into account. Did i miss something?

argue why the slow transfer is slow

Hello Friends, My task is to find out why one trace is slow.

slow --> https://drive.google.com/open?id=1w__DGZUtosFEC1AKaYBZjRSvjeJa5phZ https://www.cloudshark.org/captures/558da2ccd0e6 fast ---> https://drive.google.com/open?id=1DBQP_OxUxnp45uaHa0REbK4znupVs0oThttps://www.cloudshark.org/captures/0df849fe9447

Both the capture is made near the server via TAPs.

From my findings the slow transfer is slow because of the nature of the application. The application sends some data to sever and the server only answers after resumption of this application data. Both the traces have the same pattern of packet flow in the sense that the server waits still the client sends some data. As the RTT of the slow transfer is high the total duration is longer. Can anyone find some other reason for this?

I could calculate the slow transfer took 12 seconds as there are 253 packets send by the client which took the time equal or grater than to RTT which is 2530ms. There are 2 packets sent after the re transmission time out which is took 3041 ms. Thus the network time spend by the slow transfer is 5571ms. The time which the server took till the capture point is not taken into account. Did i miss something?

argue why the slow transfer is slow

Hello Friends, My task is to find out why one trace is slow.

slow --> https://www.cloudshark.org/captures/558da2ccd0e6 fast ---> https://www.cloudshark.org/captures/0df849fe9447

Both the capture is made near the server via TAPs.

From my findings the slow transfer is slow because of the nature of the application. The application sends some data to sever and the server only answers after resumption of this application data. Both the traces have the same pattern of packet flow in the sense that the server waits still the client sends some data. As the RTT of the slow transfer is high the total duration is longer. Can anyone find some other reason for this?

I could calculate the slow transfer took 12 seconds as there are 253 packets send by the client which took the time equal or grater than to RTT which is 2530ms. There are 2 packets sent after the re transmission time out which is took 3041 2734 ms. Thus the network time spend by the slow transfer is 5571ms. 5264ms. The time which the server took till the capture point is not taken into account. Did i miss something?