Overview |
Scalable TCP and Reno TCP from SLAC to CERN |
Scalable TCP and Reno TCP from SLAC to NIKHEF |
Scalable TCP and Reno TCP from SLAC to APAN |
High Speed TCP and Reno TCP from SLAC to Caltech |
Two Reno TCP streams from SLAC to CERN |
Two Reno TCP streams from SLAC to APAN
In this page we run tests using two single streams from two different machines
each using a different TCP stack 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 the Remote
Host.
We display the values of the throughput of the two streams every 5 seconds. |
To read about how an Iperf single stream using a new TCP stack
performs versus multiple Reno streams,
you can follow this link.
We tested the following stacks:
- Scalable TCP. It is a simple change to the traditional TCP
congestion control algorithm: the increase after dropping is exponential
instead of linear. More information can be found at the Scalable TCP
principal web page.
- HighSpeed TCP. It is part of the web100
package. It is a modification to TCP's congestion control mechanism for use
with TCP connections with large congestion windows, more details at the
HighSpeed TCP home page.
- Fast TCP. This protocol is developed at the California
Institute of Technology; read more at the
Fast TCP home page. Tests
comparing a Fast TCP single stream versus a Reno TCP single stream are reported here.
Tests comparing a Fast TCP single stream versus Reno TCP multiple streams are
reported here.
This is the page that reports a summary of High Speed
TCP, Fast TCP, Scalable TCP vs Reno single stream.
Window size = 8 MB
Window size = 8 MB
Window size = 8 MB
