Hi, Alejandro, <br><br>I have some lab test result for your reference. <br><br>Test topology:<br><br>vista linux 2.6.15 (tc) Linux 2.6.24 (reno, bic, vegas ....) <br>Client ---------------- WAN emulator ----------------------- Server <br>
<br>Server acts as sender, transfer a 2MB file.<br><br>(1) Simulate wireless connection<br>tc qdisc add dev eth0 root handle 1: netem limit 50000 delay 200ms 50ms drop 3 50% duplicate 0 corrupt 1 recorder 5 25 gap 1<br>tc qdisc add dev eth1 root handle 1: netem limit 50000 delay 200ms 50ms drop 3 50% duplicate 0 corrupt 1 recorder 5 25 gap 1<br>
TCP Stack Rate(KBps) <br>bic 25.7<br>cubic 36.8<br>highspeed 28.4<br>htcp 26.8<br>hybla 24.7<br>lp 22.1<br>scalable 28.6<br>
vegas 16.2<br>veno 26.8<br>westwood 25.7<br>illinois 32.5<br>yeah 33.6<br>reno 16.1<br><br>(2) Simulate US-ASIA<br>tc qdisc add dev eth0 root handle 1: netem limit 50000 delay 175ms 50ms drop 2 duplicate 0 gap 0 <br>
tc qdisc add dev eth0 root handle 1: netem limit 50000 delay 175ms 50ms drop 2 duplicate 0 gap 0 <br>TCP Stack Rate(KBps) <br>bic 19.8<br>cubic 28.7<br>highspeed 19.1<br>htcp 23.7<br>
hybla 19.7<br>lp 16.2<br>scalable 26.9<br>vegas 15.5<br>veno 22.8<br>westwood 27.2<br>illinois 25.1<br>yeah 21.1<br>
reno 16.4<br><br>(3) Simulate US-US<br>tc qdisc add dev eth0 root handle 1: netem limit 50000 delay 30ms 5ms drop 0.1 duplicate 0 gap 0 <br>tc qdisc add dev eth0 root handle 1: netem limit 50000 delay 30ms 5ms drop 0.1 duplicate 0 gap 0 <br>
TCP Stack Rate(KBps) <br>bic 310<br>cubic 402<br>highspeed 308<br>htcp 254<br>hybla 303<br>lp 263<br>scalable 325<br>
vegas 195<br>veno 292<br>westwood 298<br>illinois 326<br>yeah 332<br>reno 272<br><br>In my test, vegas doesn't perform better than others, but I guess vegas will perform better when network path has long queuing. hope this help!<br>
<br>-Adam<br><br><div class="gmail_quote">On Tue, Jul 8, 2008 at 6:57 AM, Alejandro Cabrera Obed <<a href="mailto:aco1967@gmail.com">aco1967@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Dear all, I have a network scenario with several Windows XP and Linux<br>
Debian Etch boxes acting as servers and clients, using typical TCP<br>
traffic like FTP, HTTP, SSH -among others-.<br>
<br>
Our boxes mainly have TCP Reno as the TCP congestion avoidance<br>
algorithm. But we see that TCP Vegas has a better response to<br>
congestion because it uses round-trip time measure to control the<br>
transfer rate, opposite to Reno that uses packet loss. And we see<br>
there are other congestion avoidance algorithm like New Reno, Bic,<br>
Cubic, etc.<br>
<br>
So, what is the best congestion avoidance algorithm nowadays taking<br>
into account the response time to congestion situations ??? What do<br>
you recommend to me ???<br>
<br>
Special thanks<br>
<br>
<br>
--<br>
Alejandro Cabrera Obed<br>
<a href="mailto:aco1967@gmail.com">aco1967@gmail.com</a><br>
<a href="http://www.alejandrocabrera.com.ar" target="_blank">www.alejandrocabrera.com.ar</a><br>
<br>
_______________________________________________<br>
Iccrg mailing list<br>
<a href="mailto:Iccrg@cs.ucl.ac.uk">Iccrg@cs.ucl.ac.uk</a><br>
<a href="http://oakham.cs.ucl.ac.uk/mailman/listinfo/iccrg" target="_blank">http://oakham.cs.ucl.ac.uk/mailman/listinfo/iccrg</a><br>
</blockquote></div><br>