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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

9.2. Preferential Flow H<strong>and</strong>ling Using DiffServ 223<br />

cwnd <strong>and</strong> ssthresh (packets)<br />

30000<br />

25000<br />

20000<br />

15000<br />

10000<br />

5000<br />

cwnd<br />

ssthresh<br />

cwnd <strong>and</strong> ssthresh (packets)<br />

30000<br />

25000<br />

20000<br />

15000<br />

10000<br />

5000<br />

cwnd<br />

ssthresh<br />

0<br />

0 50 100 150 200 250 300<br />

Time (seconds)<br />

(a) 70% AF with Congestion Moderation<br />

0<br />

0 50 100 150 200 250 300<br />

Time (seconds)<br />

(b) 70% AF without Congestion Moderation<br />

cwnd <strong>and</strong> ssthresh (packets)<br />

30000<br />

25000<br />

20000<br />

15000<br />

10000<br />

5000<br />

cwnd<br />

ssthresh<br />

cwnd <strong>and</strong> ssthresh (packets)<br />

30000<br />

25000<br />

20000<br />

15000<br />

10000<br />

5000<br />

cwnd<br />

ssthresh<br />

0<br />

0 50 100 150 200 250 300<br />

Time (seconds)<br />

(c) 90% AF with Congestion Moderation<br />

0<br />

0 50 100 150 200 250 300<br />

Time (seconds)<br />

(d) 90% AF without Congestion Moderation<br />

Figure 9.23: Effect of Congestion Moderation on HSTCP with 70% <strong>and</strong> 90% AF<br />

allocation.<br />

to very low relative values.<br />

Even without congestion moderation, it was also observed that there were<br />

a few drops in cwnd <strong>and</strong> goodput, which were briefly raised (not through slow<br />

start nor congestion avoidance) to their previous values before the drop. The<br />

cause of this action was found to be due to Linux undo’s [SK02] during<br />

which the ssthresh <strong>and</strong> cwnd values are reduced due to an indication of<br />

congestion. However, shortly afterwards, DSACK (See Section 4.5.5) <strong>and</strong>/or<br />

ack information infers that the congestion event was in fact not necessary <strong>and</strong><br />

therefore the TCP cwnd <strong>and</strong> ssthresh values are readjusted to the previously<br />

recorded values.<br />

Without congestion moderation, HSTCP shows an appreciable difference

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

Saved successfully!

Ooh no, something went wrong!