ndt-users list created

[Matt Mathis <>]

I am just guessing here but NDT is actually quite busy: it reads
Web100 vars every millisecond, and runs 2 different packet capture
tools.  Although one would hope that all of these activities run in
different cores it would not surprise me to discover that the maximum
data rate is somewhat depressed.

Web100 and related tools can't do any meaningful performance debugging
when the bottleneck is very fine grained resource contention within
the sender itself, especially CPU, bus bandwidth and lock contention.

Thanks,
--MM--
The best way to predict the future is to create it.  - Alan Kay




On Sat, May 28, 2011 at 7:02 PM, Brian Tierney 
<>
 wrote:
>
>
> I'm seeing the same thing  (much higher results reported by iperf compared 
> to NDT)
>
> Is this expected?
>
>
> On May 2, 2011, at 8:26 AM, 
> <>
>  
> <>
>  wrote:
>
>> Dear members:
>> I have tried several approaches to use NDT on a server with a 10 gigabit
>> interface.  I wonder if there are any limitations on the server to client
>> tests.  I have not been able to get more than around 2.6 gigs
>> server-to-client.  The client-to-server test can go over 9 gigs even 
>> without
>> extensive tuning.  On the same server, I can get over 9 gigs in each 
>> direction
>> to a neighbor server using iperf tests.
>>
>> Are there any tips on running NDT on a 10gig capable server?
>>
>> Thanks,
>> Nat Stoddard
>
>
>