Skip to content


Michele Weigle edited this page Jun 11, 2015 · 4 revisions


The validation experiments used the connection vectors from our CCR 2006 paper (src direction uses outbound.cvec, dst direction uses inbound.cvec). The TCL script used is tmix.tcl.

Experiment topology:

We ran 8 experiments, each run for 3600 seconds:

  • one-way TCP lossy, FIN 1 s
  • one-way TCP lossless, FIN 1 s
  • one-way TCP lossless, FIN 100 ms
  • one-way TCP lossless, FIN 10 ms
  • Full-TCP lossy, FIN 1 s
  • Full-TCP lossless, FIN 1 s
  • Full-TCP lossless, FIN 100 ms
  • Full-TCP lossless, FIN 10 ms

###FIN Wait Times### For many connection vectors, there was no TCP FIN packet recorded, so we do not know exactly when the connection was completed. For many metrics, we need to know the duration of the connection. For those connections that do not have a FIN, we inserted an artificial FIN.

The FIN time (1 sec, 100 ms, 10 ms) in the experiment indicates the time between when the last data unit was sent and the sending of the artificial FIN. Shorter FIN times result in shorter connections, lower active connections, and faster runtimes.

The impact of the artificial FIN is most apparent for one-way TCP. Waiting longer before sending the artificial FIN ensures that all packets in the connection have been received before the TCP connection closes, producing results that more closely match the original and testbed. The tradeoff is that the running time and memory usage are increased. We show all results so that users are aware of the tradeoff. The default value for the FIN wait time is 1 second.


Each set of graphs (except runtime) includes the following metrics:

  • number of active connections each second
  • CDF of goodput for each completed connection
  • packet arrivals per second in each direction
  • CDF of HTTP response times for each completed connection
  • CDF of RTTs for each connection
  • throughput per second in each direction

Validation Graphs

You can’t perform that action at this time.