questions about udp
- To: iperf-users --at-- dast.nlanr.net
- Subject: questions about udp
- From: yang hua <harriet_yang --at-- yahoo.com>
- Date: Thu, 29 Sep 2005 12:03:58 -0700 (PDT)
- Content-transfer-encoding: 8bit
- Content-type: text/plain; charset=iso-8859-1
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ZG6Q8UMZXKAXTA+/eZhQHj0/IX5oPu8ennlUJezl38s+goAXZkcFDUIJFelJXRdGdz+APbgXXFicpgzZcJW1Y+KvKFy8EFrghNVLE92cUbGy7XR+epSzaBUw7VHrTxEB1EEU4nAi5QIuYLA4daAlTMLhWal4g08gF12eesLqhtg= ;
- Reply-to: iperf-users --at-- dast.nlanr.net
- Sender: owner-iperf-users --at-- dast.nlanr.net
Dear all,
I was running iperf to test the network throughput. I
have an 802.11g client and a server connected to the
access point via 100BaseT cable. The client is pushing
data to the server. At the end of this message I
attached the command and output from the server side.
Can anyone tell me why the first 5 sec of the output
has such a weird loss/total?
Another question is about datagram?s side. I checked
out email archive and found that if you use ?iperf ?s
?u? at the server side, you can send whatever length
you want at the client side. Is that true even if I
send datagram that is larger than 1470 bytes? I tried
and the server reported ?message too long?, which is
well expected. So, do we have a way of start the
server that accepts datagrams of any size?
A last question is about the network efficiency. Since
my server is connected to the AP via 100BasedT, so we
don?t have any bottleneck there. The client is
connected wirelessly via 802.11g to the AP, naturally
I think ?2000bytes? of datagram is a good choice for
the wireless mac since 802.11 MTU is 2304 bytes. What
I don?t understand is that when I set the datagram
length as 2000bytes, I only see somewhere around
13Mbits/sec throughput, while if I set it as ?32k?, I
can get as much as ?25Mbits/sec?. Can anyone enlighten
me on this issue? I am really confused now.
******client side command ******************
iperf -c serveraddr -u -i 5 -l 32k -b 50m -t 300s
******server side command and output *********
C:\Documents and Settings\hyang13\Desktop>iperf -s -u
-i 5 -l 32k
------------------------------------------------------------
Server listening on UDP port 5001
Receiving 32768 byte datagrams
UDP buffer size: 8.00 KByte (default)
------------------------------------------------------------
[1968] local 192.168.3.15 port 5001 connected with
192.168.3.10 port 1283
[ ID] Interval Transfer Bandwidth
Jitter Lost/Total Datagr
[1968] 0.0- 5.0 sec 13.5 MBytes 22.6 Mbits/sec
7.375 ms 1342198862/ 431
1e+008%)
[1968] 5.0-10.0 sec 13.8 MBytes 23.1 Mbits/sec
8.578 ms 0/ 441 (0%)
[1968] 10.0-15.0 sec 13.3 MBytes 22.3 Mbits/sec
7.288 ms 0/ 426 (0%)
[1968] 15.0-20.0 sec 13.6 MBytes 22.8 Mbits/sec
6.773 ms 0/ 435 (0%)
[1968] 20.0-25.0 sec 14.0 MBytes 23.4 Mbits/sec
7.200 ms 0/ 447 (0%)
[1968] 25.0-30.0 sec 13.9 MBytes 23.4 Mbits/sec
6.815 ms 0/ 446 (0%)
[1968] 30.0-35.0 sec 14.0 MBytes 23.5 Mbits/sec
6.973 ms 0/ 448 (0%)
[1968] 35.0-40.0 sec 13.6 MBytes 22.8 Mbits/sec
7.254 ms 0/ 435 (0%)
[1968] 40.0-45.0 sec 13.9 MBytes 23.3 Mbits/sec
7.192 ms 0/ 444 (0%)
[1968] 45.0-50.0 sec 12.3 MBytes 20.7 Mbits/sec
7.165 ms 0/ 394 (0%)
[1968] 50.0-55.0 sec 14.0 MBytes 23.5 Mbits/sec
6.911 ms 0/ 449 (0%)
[1968] 55.0-60.0 sec 14.0 MBytes 23.5 Mbits/sec
7.716 ms 0/ 449 (0%)
[1968] 60.0-65.0 sec 13.9 MBytes 23.3 Mbits/sec
7.101 ms 0/ 444 (0%)
[1968] 65.0-70.0 sec 13.8 MBytes 23.1 Mbits/sec
7.009 ms 0/ 440 (0%)
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com