Fast TCP on production links,
one Fast TCP single stream vs.
one Reno TCP single stream

Main Page of TCP Stacks on production links | High Speed TCP single streams versus a Reno TCP single stream | Scalable TCP single streams versus a Reno TCP single stream | Scalable TCP single stream versus Reno TCP multiple streams | Fast TCP single stream versus Reno TCP multiple streams | Bulk throughput measurements
Fabrizio Coccetti and Les Cottrell. Created 2April '03, last update 3 April '03

Overview | Fast TCP and Reno TCP from SLAC to CERN | Fast TCP and Reno TCP from SLAC to APAN | Fast TCP and Reno TCP from SLAC to NIKHEF | Fast TCP and Reno TCP from SLAC to Caltech

Overview

In this page we run tests using two single streams from two different machines, one using the FastTCP stack and the other using Reno TCP. Tests are performed to the same destination machine. All measures have a standard MTU (1500B) and txqueuelen (100packets), the TCP window was chosen appropriately big (8 MB).

An Iperf single stream is started from S1 to the Remote Host.
At the same time, another Iperf single stream is started from S2 to the Remote Host.
We display the values of the throughput of the two streams every 5 seconds.

This is the main page for the tests we are conducting using new TCP stacks on production links.
In another page, it is available a comparison between one Fast TCP single stream and Reno TCP multiple streams, from SLAC to CERN.