ndt-users list created

["Stout, Jeff" <>]

To be vague as possible here on that. We have basically told everyone no 
testing of Windows 7 computers on NDT. The results have been horrid. Dual 
boot on the same machine with XP or Linux Mint and the speeds are always 
right on the money. I have tried to adjust the server settings and I don't 
see anything to indicate why we get 1/2 or less speeds with 7 and even Vista 
from time to time. But I don't count Vista(WindowME2) as a operating system. 

Jeffery A. Stout
Network and Router Management
Insight Road Runner Abuse
Insight Communications
3770 E. Livingston Ave
Columbus, OH 43227
Office: 1-614-338-7063
Cell: 1-614-496-3579

AIM: jstout5114

________________________________________
From: 

 
[]
 on behalf of Bob Gerdes 
[]
Sent: Monday, February 13, 2012 5:02 PM
To: 

Subject: Windows Configuration issues when testing to NDT servers

Greetings,

We have been doing a series of NDT tests on one of our campuses, and found 
that there is inconsistent results between Linux systems and Windows (XP and 
7) systems. We have used the recommendations from DrTCP (noted on 
fasterdata.es.net) and the psc.edu site. And the Windows results consistently 
look much worse than the Linux systems. Has anyone been able to get better 
results with Windows and could suggest specific configuration settings?

One additional note is that there was a 1.5% of packets that arrived out of 
order.

Any advice would be greatly appreciated.
      Thanks,
        Bob

  Bob Gerdes
  Office of Instructional and Research Technologies (OIRT)
  Office of Information Technology (OIT)
  Rutgers, The State University
  ASB Annex I, room 101G, Busch Campus
  56 Bevier Road, Piscataway, NJ 08854
  Phone: (732) 445-1438   Fax: 445-5539

> We followed this reference which talks about tuning Windows XP:
>   http://www.psc.edu/networking/projects/tcptune/
>         as well as this
>   http://fasterdata.es.net/fasterdata/host-tuning/
>
> Also, we ran DrTCP, rebooted and still the exact same results from my XP 
> machine...
>
>> using linux in room 313
>>
>> Camden-to-Camden:
>> running 10s outbound test (client to server) . . . . .  898.23 Mb/s
>> running 10s inbound test (server to client) . . . . . . 880.40 Mb/s
>>
>> Camden-to-Newark:
>> running 10s outbound test (client to server) . . . . .  478.16 Mb/s
>> running 10s inbound test (server to client) . . . . . . 518.90 Mb/s
>>
>> Camden-to-NB:
>> running 10s outbound test (client to server) . . . . .  841.83 Mb/s
>> running 10s inbound test (server to client) . . . . . . 834.33 Mb/s
>>
>> and, when we switch the PC next to Linux system in BSB 113 to 1Gb
>> (uses Windows 7), we get:
>>
>> Camden-to-Camden:
>> running 10s outbound test (client to server) . . . . .  272.50 Mb/s
>> running 10s inbound test (server to client) . . . . . . 726.08 Mb/s
>>
>> Camden-to-Newark:
>> running 10s outbound test (client to server) . . . . .  55.24 Mb/s
>> running 10s inbound test (server to client) . . . . . . 219.61 Mb/s
>>
>> Camden-to-NB:
>> running 10s outbound test (client to server) . . . . .  60.01 Mb/s
>> running 10s inbound test (server to client) . . . . . . 229.60 Mb/s
>>
>> comparable to Windows XP at Gig speed.
>>
>> It must be WINDOWS?  and, it's configuration?
>>
>> So, is there an optimal setting for a Windows machine that I could try?
>>
>>>
>>> With the 3 systems tested giving basically the same results, this
>>> kind of eliminates the possibility of cable issues or port
>>> malfunctioning as well as OS and NIC issues.
>>>
>>> The traffic shaping and receiver limited issue seem puzzling.
>>>>
>>>>>> From two linux servers, got the following:
>>>>>>
>>>>>> From Office System (165.230.105 subnet):
>>>>>> Camden-to-Camden:
>>>>>>  running 10s outbound test (client to server) . . . . .  862.62 Mb/s
>>>>>>  running 10s inbound test (server to client) . . . . . . 850.73 Mb/s
>>>>>>
>>>>>> Camden-to-Newark:
>>>>>>  running 10s outbound test (client to server) . . . . .  574.44 Mb/s
>>>>>>  running 10s inbound test (server to client) . . . . . . 519.07 Mb/s
>>>>>>
>>>>>> Camden-to-NB:
>>>>>>  running 10s outbound test (client to server) . . . . .  846.37 Mb/s
>>>>>>  running 10s inbound test (server to client) . . . . . . 816.39 Mb/s
>>>>>>
>>>>>>
>>>>>> From clamshell (165.230.99 subnet):
>>>>>> Camden-to-Camden:
>>>>>>  running 10s outbound test (client to server) . . . . .  882.16 Mb/s
>>>>>>  running 10s inbound test (server to client) . . . . . . 891.93 Mb/s
>>>>>>
>>>>>> Camden-to-Newark:
>>>>>>  running 10s outbound test (client to server) . . . . .  490.35 Mb/s
>>>>>>  running 10s inbound test (server to client) . . . . . . 531.92 Mb/s
>>>>>>
>>>>>> Camden-to-NB:
>>>>>>  running 10s outbound test (client to server) . . . . .  838.58 Mb/s
>>>>>>  running 10s inbound test (server to client) . . . . . . 869.51 Mb/s
>>>>>>
>>>>>> The NDT servers that I used were:
>>>>>>   ndt-cam.rutgers.edu
>>>>>>   ndt-nwk.rutgers.edu
>>>>>>   ndt-nbp.rutgers.edu