search

evristzam / ndt

Automatically exported from code.google.com/p/ndt
Other
0 stars 0 forks source link

Recive and Send buffer problem not reported in statistics window. #6

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1. Connect server and client in a 1GBit Switch
2. Start both servers (fakewww and web100)
3. Set the following tcp paramters in both server and client.
    echo 0 > /proc/sys/net/ipv4/tcp_moderate_rcvbuf
    echo 4194304 > /proc/sys/net/core/wmem_max
    echo 4194304 > /proc/sys/net/core/rmem_max
    echo "4096 32768 32768" > /proc/sys/net/ipv4/tcp_rmem
    echo "4096 16384 16384" > /proc/sys/net/ipv4/tcp_wmem
    echo "1" > /proc/sys/net/ipv4/tcp_timestamps
    echo "0" > /proc/sys/net/ipv4/tcp_window_scaling
    echo "1" > /proc/sys/net/ipv4/tcp_sack
    echo "1" > /proc/sys/net/ipv4/tcp_ecn

4. Click the start button to start the test and wait till client complete
the test.
5. Check the staticstics window

What is the expected output? What do you see instead?
Since Throughput can be improved by increasing the recive and send buffers
messege should be displayed in statistics window.
But No message has been displayed syaing that by increasing the recive and
send buffers throughput can be increased. And also the buffer sizes
displayed in the more details page is also not correct. Server receive
buffer showed as 8K instead of 32k  and client receive buffer is showed as
22k instead of 32k.

What version of the product are you using? On what operating system?
NDT server 3.6.0 
Client : Linux (Ubuntu 9)

Please provide any additional information below.

Original issue reported on code.google.com by sekharn...@gmail.com on 27 Feb 2010 at 1:24

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by sekharn...@gmail.com on 27 Feb 2010 at 1:41

GoogleCodeExporter commented 9 years ago 
Removing the 'Priority' tag and replacing with a 'Severity' tag.  Un-assigning 
QA team as owner of the bug.

Original comment by jwzuraw...@gmail.com on 1 Mar 2010 at 12:26

GoogleCodeExporter commented 9 years ago

Original comment by jwzuraw...@gmail.com on 10 Mar 2010 at 8:59

GoogleCodeExporter commented 9 years ago 
Re-verified with V3.6.3 and this bug is not yet fixed. The problem is reported 
with the following parameters at client. 

        echo 0 > /proc/sys/net/ipv4/tcp_moderate_rcvbuf
    echo 4194304 > /proc/sys/net/core/wmem_max
    echo 4194304 > /proc/sys/net/core/rmem_max
    echo "4096 32768 32768" > /proc/sys/net/ipv4/tcp_rmem
    echo "4096 16384 4194304" > /proc/sys/net/ipv4/tcp_wmem
    echo "1" > /proc/sys/net/ipv4/tcp_timestamps
    echo "0" > /proc/sys/net/ipv4/tcp_window_scaling
    echo "1" > /proc/sys/net/ipv4/tcp_sack
    echo "1" > /proc/sys/net/ipv4/tcp_ecn

Original comment by sekharn...@gmail.com on 10 Jun 2010 at 6:32