TCP Evaluation Suite
Evaluating New Congestion Control Schemes and Its Impact on Standard TCP NewReno
Home › Simulation Environmnet › File Formats 2

Simulation File Formats 2

Jul 18, 2007 by cesar

In addition to the summaries presented in the Simulation File Format 1, the "script.tcl" also generates several files inside the directory DATA4. These files however, present a more fine-grained information about the behavior of the flows in a 10 msec scale. There will be "Y" congestion window files depending on the number of the long lived flows, and it is also logged 10 msec queueing status of every one of the "core links". The following are the formats of these files:

  • file: prot1prot2_cwnd_X_Z.out (where X = one random seed of this environment, and Z = flow ID)
  • 74.60 410.049 307.0 12309560 13.617454545454548 74.70 410.049 307.0 12309560 13.617454545454548 74.80 410.049 307.0 12928660 17.032800000000005 74.90 426.021 309.0 12928660 17.032800000000005

    This is the congestion window dynamics of a single flow. It shows the following information: 1) the monitoring of TCP internal variable happen every 10 msec 2) the actual congestion window of the flow 3) the smoothed RTT perceived by this flow 3) the total number of bytes already transferred so far and 4) the goodput of this flow in Mbps. Therefore, the line "74.60 410.049 307.0 12309560 13.617454545454548" presents data of this flow "prot1prot2_cwnd_5_4.out. At time, 74.60 sec the congestion window of this flow was 410, the srtt of the flow 307, the number of bytes transferred 12MB and the goodput 13.6Mbps.

    • file: queues_X_AA.out (where X = one random seed, and AA = core link LIKE "01", from NODE 0 to NODE 1)
    • 48.50 1179790 1234 2309325 2741848086 2307728 2740339196 363 329100 48.60 391870 352 2319362 2753578856 2318630 2752839566 380 347420 48.70 0 0 2328331 2763098656 2327951 2762751236 380 347420 48.80 0 0 2336290 2770812586 2335910 2770465166 380 347420

      This file presents the queue dynamics of the core links. It's important to remember that in ns-2 the queues are implemented inside the "LINKS" thus every link has a queue. We then present one of the possible queues (depending on the direction - forward/backward and size of the core) internal information using a 10 msec granularity. In this example case, we have the following information:

      $1 = log reported every 10 msecs $2 = average number of bytes inside the queue $3 = average number of packets inside the queue $4 = cumulative number of packets received $5 = cumulative number of bytes received $6 = cumulative number of packets sent $7 = cumulative number of bytes sent $8 = cumulative number of packets lost $9 = cumulative number of bytes lost