Menu
▾
▴
RE: [coLinux-users] loopback and some question marks on speed
|
From: Sunil <fu...@ya...> - 2006-03-30 02:19:53
|
partial good news. The throughput is related to window size in a wierd way for colinux and loopback connection. 1. It doesn't matter how high I set the TCP window size on colinux, 192.168.0.0 network is much faster (220 vs 30) than 10.3.75.0 loopback network. 2. High values of TCP windows size on windows XP side give the boost to 10.3.75.0 network beyond 192.168.0.0 network. This also requires a high window size on colinux, which is understandable. C:\Program Files\IPerf>iperf -s ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 64.2 KByte (default) ------------------------------------------------------------ [1920] local 10.3.75.1 port 5001 connected with 10.3.75.2 port 46177 [ ID] Interval Transfer Bandwidth [1920] 0.0-10.1 sec 39.7 MBytes 31.5 Mbits/sec [1920] local 192.168.0.3 port 5001 connected with 192.168.0.11 port 41019 [ ID] Interval Transfer Bandwidth [1920] 0.0-10.0 sec 272 MBytes 217 Mbits/sec close failed: Successful WSAStartup not yet performed. C:\Program Files\IPerf>iperf -s -w 256K ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 256 KByte ------------------------------------------------------------ [1920] local 10.3.75.1 port 5001 connected with 10.3.75.2 port 46174 [ ID] Interval Transfer Bandwidth [1920] 0.0-10.0 sec 157 MBytes 126 Mbits/sec [1920] local 192.168.0.3 port 5001 connected with 192.168.0.11 port 41016 [ ID] Interval Transfer Bandwidth [1920] 0.0-10.0 sec 278 MBytes 223 Mbits/sec C:\Program Files\IPerf>iperf -s -w 640K ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 640 KByte ------------------------------------------------------------ [1920] local 10.3.75.1 port 5001 connected with 10.3.75.2 port 46179 [ ID] Interval Transfer Bandwidth [1920] 0.0-10.0 sec 356 MBytes 285 Mbits/sec [1920] local 192.168.0.3 port 5001 connected with 192.168.0.11 port 41021 [ ID] Interval Transfer Bandwidth [1920] 0.0-10.0 sec 278 MBytes 222 Mbits/sec close failed: Successful WSAStartup not yet performed. At 1280K, it increased further but iperf died abnormally on ctrl-c...:) I think this is interesting. Why would increasing the tcp window size on xp give boost to one but not the other interface? Thanks, -Sunil Sunil <fu...@ya...> wrote: How can the direction make order of magnitude difference? I notice in the data that the windows uses TCP window size of 64KB for both client and server, while colinux uses 16KB for client and 85KB for server iperf. Are these configured in the kernel? look at these: root@co-amd-pc ~ $ iperf -c 10.3.75.1 ------------------------------------------------------------ Client connecting to 10.3.75.1, TCP port 5001 TCP window size: 16.0 KByte (default) ------------------------------------------------------------ [ 3] local 10.3.75.2 port 51361 connected with 10.3.75.1 port 5001 [ 3] 0.0-10.0 sec 39.1 MBytes 32.8 Mbits/sec root@co-amd-pc ~ $ iperf -s ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 85.3 KByte (default) ------------------------------------------------------------ [ 4] local 10.3.75.2 port 5001 connected with 10.3.75.1 port 3215 [ 4] 0.0-10.0 sec 687 MBytes 576 Mbits/sec Thanks, Sunil Matt Dockerty <mat...@18...> wrote: I should have mentioned YMMV. Networking doesn't seem like an exact science in Colinux at this alpha stage and I only got these levels of performance through blind trial and error. My setup is a MS Loopback Adapter on a 192.168 subnet and a TAP adapter on same. My physical LAN is on a 10.10 subnet and Internet Connection Sharing is enabled. My network config in Colinux is simply this: Like Holger says 10Mbps means nothing since the loopback driver is only capped by the limitations of the software. Here are the results I'm getting: colinux ~ # iperf -c 192.168.0.1 ------------------------------------------------------------ Client connecting to 192.168.0.1, TCP port 5001 TCP window size: 16.0 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.0.100 port 1767 connected with 192.168.0.1 port 5001 [ 3] 0.0-10.7 sec 69.1 MBytes 54.0 Mbits/sec colinux ~ # iperf -s ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 85.3 KByte (default) ------------------------------------------------------------ [ 4] local 192.168.0.100 port 5001 connected with 192.168.0.1 port 2146 [ 4] 0.0-10.0 sec 125 MBytes 105 Mbits/sec -- Matt > -----Original Message----- > From: col...@li... > [mailto:col...@li...] On Behalf > Of Holger Krull > Sent: 29 March 2006 07:59 > To: colinux > Subject: Re: [coLinux-users] loopback and some question marks on speed > > Sunil schrieb: > > > way? Why are loopback adapters shown as 10Mbps? Is there a > way to change > > that? > > That is just a label without meaning. > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking > scripting language > that extends applications into web and mobile media. Attend > the live webcast > and join the prime developer group breaking into this new > coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720& dat=121642 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users --------------------------------- New Yahoo! Messenger with Voice. Call regular phones from your PC for low, low rates. --------------------------------- New Yahoo! Messenger with Voice. Call regular phones from your PC and save big. |