05.08.2014 Views

An Investigation into Transport Protocols and Data Transport ...

An Investigation into Transport Protocols and Data Transport ...

An Investigation into Transport Protocols and Data Transport ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

9.1. Transfer Tests Across Dedicated Private Wide Area Networks 205<br />

aggressive impact of ScalableTCP. Both HSTCP <strong>and</strong> H-TCP appear to have<br />

similar impact properties, with H-TCP being a little bit more aggressive with<br />

larger numbers of St<strong>and</strong>ard TCP flows.<br />

9.1.7 Discussion of Results<br />

In order to better underst<strong>and</strong> the lack of b<strong>and</strong>width utilisation of a single<br />

New-TCP flow when competing against CBR traffic (See Figure 9.3),<br />

Figure 9.12 shows the cwnd <strong>and</strong> goodput traces of the various New-TCP<br />

algorithms with 200Mbit/sec <strong>and</strong> 600Mbit/sec CBR background loads. For<br />

HSTCP, at low background loads <strong>and</strong> after congestion, the value of cwnd<br />

diminished below the value of ssthresh. It is this decrease in cwnd after<br />

congestion that lowers the goodput even though extra b<strong>and</strong>width is available.<br />

Similar results were observed for ScalableTCP. However, unlike HSTCP,<br />

there are intermittent periods whereby the cwnd actually drops to very low<br />

values <strong>and</strong> ScalableTCP has to grow cwnd all the way from very low values of<br />

cwnd upto the point of congestion. At lower goodputs, ScalableTCP is able<br />

to function appropriately, with a very small back-off per congestion event<br />

which results in a slightly higher goodput compared to the other algorithms.<br />

It was observed that H-TCP’s dynamic is not as severely affected under<br />

large b<strong>and</strong>widths as that of ScalableTCP or HSTCP, which explains the<br />

slightly higher value of H-TCP under MB-NG.<br />

As the TCP specifications [Jac88] state that the cwnd should be set to<br />

the calculation of ssthresh upon congestion (plus 3 packets for the duplicate<br />

acknowledgments), is it surprising that the values of ssthresh for these tests<br />

show that there is no recalculation. This suggests that these drops in cwnd

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!