<<  Force10 Loop-Back   |   TCP / UDP Tests   |   Table of Contents   |   Bandwidth Interval Plots  >   |   RBUDP & UDT Flows  >>

Single Flow UDT & Multiple Flows TCP

Description

The goal in these tests is to study the TCP friendliness of the UDT protocol. This has been done by measuring the effect of one large UDT flow upon many, small TCP flows. In these tests the UDT flow will be started as first and after some time the TCP flows, or the other way around. As stated in the "Introduction", a modified version of the Iperf traffic generator is used to be able to shape the TCP bandwidth sufficiently. 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 (Iperf option -P; implemented with the pthread library).

In these tests the following parameters have been varied:

Considering the (almost) zero RTT it makes no sense here to vary the TCP window size. Therefore, a value of 128 KBytes have been selected. This value appeared to be rather optimal in this situation. Also a fixed value of 8000 bytes have been selected for the TCP socket buffer sizes. This value seems to be rather optimal in many cases. The dest duration of the UDT 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.


<<  Force10 Loop-Back   |   TCP / UDP Tests   |   Table of Contents   |   Bandwidth Interval Plots  >   |   RBUDP & UDT Flows  >>