Previous Topic: Increase in Data Transfer Time and Observations CountNext Topic: Increase in Data Transfer Time and Decrease in Observations Count


Data Transfer Time = 0 (Ping-Pong Application)

A "Ping-Pong" application sends single-packet responses to most or all requests; it is an application problem. The management console calculates the Data Transfer Time by subtracting the time stamp associated with the last application response to the client data request from the time stamp associated with the first application response to the client data request. If the timestamps are equal, the result is 0 because only one packet was sent by the application in response to the client request, and that this packet must be acknowledged at the application layer before the client can request the next packet.

If the amount of data needed to complete the total transaction numbers in the tens or hundreds of thousand bytes, this can cause significant throughput issues for the application because the client must wait one NRTT+ for each packet to be delivered and acknowledged by the application. If the client asked for all data in a single request, the application would respond by sending as many bytes in multiple packets at one time as the TCP active window allows it to send. This dramatically decreases the number of round trips necessary to transmit the data, and increases the performance of the application.

To verify this scenario when Data Transfer Time is equal to zero:

  1. In the Show Me menu, click Response Size.
  2. Scroll to the Data Transfer Time by Response Size view and determine if the number of data transfers less than 1.45 KBs, one segment or packet based on an Ethernet frame, is the most significant bar of the following view. This indicates that most of the packet contain a minimum of data:

    Data Transfer Time by Response Size  indicates that most of the packet contain a minimum of data.