NDT-DEV email list created

[Rich Carlson <>]

Sekhar;

The NDT readme should have a comment about this.  You need to disable 
interrupt coalescing on the server's NIC to get good data for the 
bottleneck link test.

Rich

On 2/26/2010 8:24 PM, 

 wrote:
> Status: Accepted
> Owner: sekharnv73
> Labels: Type-Defect Priority-High
>
> New issue 3 by sekharnv73: Slowest link detection in the path is not
> correct
> http://code.google.com/p/ndt/issues/detail?id=3
>
> What steps will reproduce the problem?
>
> 1. Connect server and client in a 1GBit Switch
> 2. Start both servers (fakewww and web100)
> 3. Open the browser and connect to the server.
> 4. Click the start button to start the test and wait till client complete
> the test.
> 5. Slowest link displayed as (slowest link as "622 Mbps OC-12) insted of
> 1GBit also the inbound and outbound throughput is showed more than 900MB.
>
> What is the expected output? What do you see instead?
> Slowes Link should be 1GBit ethernet and throughput should be less then the
> slowest link.
>
>
> 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.
>
> In more details window also it is showing link type as OC-12 and GigE.
>
>
>
> --
> You received this message because you are listed in the owner
> or CC fields of this issue, or because you starred this issue.
> You may adjust your issue notification preferences at:
> http://code.google.com/hosting/settings