I ran iperf as well and got poor results with both 256KB and 16Bytes
(2KB).

(desktop-pc) $ iperf -s -w 256K
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size:  256 KByte (WARNING: requested  256 KByte)
------------------------------------------------------------
[  4] local 192.168.50.223 port 5001 connected with 192.168.50.107 port 39723

(panda) # iperf -c 192.168.50.223 -w 256K -t 10                         
------------------------------------------------------------
Client connecting to 192.168.50.223, TCP port 5001
TCP window size:   256 KByte (WARNING: requested   256 KByte)
------------------------------------------------------------
[  3] local 192.168.50.107 port 39723 connected with 192.168.50.223 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-13.3 sec    200 KBytes    123 Kbits/sec


(desktop-pc) $ iperf -s -w 16
WARNING: TCP window size set to 16 bytes. A small window size
will give poor performance. See the Iperf documentation.
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 2.23 KByte (WARNING: requested 16.0 Byte)
------------------------------------------------------------
[  4] local 192.168.50.223 port 5001 connected with 192.168.50.107 port 39724
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-18.3 sec   144 KBytes  64.5 Kbits/sec

(panda) # iperf -c 192.168.50.223 -w 16 -t 10                           
WARNING: TCP window size set to 16 bytes. A small window size
will give poor performance. See the Iperf documentation.
------------------------------------------------------------
Client connecting to 192.168.50.223, TCP port 5001
TCP window size: 2.00 KByte (WARNING: requested 16.0 Byte)
------------------------------------------------------------
[  3] local 192.168.50.107 port 39724 connected with 192.168.50.223 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-18.3 sec    144 KBytes  64.5 Kbits/sec

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/709245

Title:
  ARM SMP scheduler performance bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-ubuntu/+bug/709245/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to