<<  UDT & TCP Flows   |   UDT & TCP Concl.   |   Table of Contents   |   Bandwidth Interval Plots  >   |   F10 Loop-Back Concl.  >>

Single Flow RBUDP & Multiple Flows TCP

Description

Just as for the tests described in the "Single Flow UDT & Multiple Flows TCP", the intension of these tests is to study the TCP friendliness of the RBUDP protocol and to compare it with UDT. However, there should be noted that the developers do not claim that RBUDP is TCP friendly: their most important objective is to obtain a bandwidth as high as possible. As in the UDT & TCP section the TCP friendliness has been studied by measuring the effect of one large RBUDP flow upon many, small TCP flows that are again generated with a modified version of the Iperf traffic generator. Also in these tests the RBUDP flow will be started as first and after some time the TCP flows, or the other way around. The TCP flows are generated between two sets of N DAS-2 cluster nodes which are separated in two VLAN's. To obtain sufficient diversity in the # flows, each node in the source VLAN is sending one flow to each of the N receiving nodes in the destination VLAN. A flow between sender and receiver may consist of one or more parallel streams.

In these the following parameters have been varied:

Taken into account the (almost) zero RTT it makes no sense here to vary the TCP window size. Here a value of 128 KBytes has been used which seems to be rather optimal in these tests. Also a fixed value of 8000 bytes have been selected for the TCP socket buffer sizes. Also this value seems to be in general rather optimal. The test duration of the RBUDP and TCP flows was 120 s. The delay interval after which the delayed flows are started was the half of the test duration: 60 s.

Results

In the next sub-sections some parameter cross-sections of the data sets described in the previous section will be presented.


<<   UDT & TCP Flows   |   <   UDT & TCP Concl.   |   Table of Contents   |   Bandwidth Interval Plots   >   |   F10 Loop-Back Concl.  >>