The NDT performs 2 TCP throughput tests between your desktop computer and this NDT server. First, data is streamed for 10 seconds from your desktop to the server and then a second 10 second test is performed in the opposite direction. A Web100 modified linux kernel captures detailed statistics on these TCP data flows. This data is then analyzed to determine why the connection achieved the throughput results it reported.
End-to-End performance depends upon a number factors. One of the biggest factors is setting the tunable network parametes to the proper value. There are several web sites that provide detailed tuning instructions for various Operating Systems. Two of the best are:
If a large number of retransmissions occur, check the duplex and speed setting on your host and the network switch it attaches to (duplex mismatches are a serious problem due to broken autonegoation protocols). Extremely long round trip times (over 1 sec) ususally indicate that a network router or switch is congested leading to long queuing times. Contact your local network administrator for help in solving this problem
The Bandwidth * Delay product is reported at the bottom of the "more details" page. Throughput limits for the NDT server's transmit buffer, your clients receive buffer, and the network infrastructure. You may use these numbers as a guide to determining what your client's receive buffer is currently set to. Divide the buffer size by the reported round trip time (RTT) to calculate the throughput value.
For more info on TCP tuning, visit cable/dsl tuning or dslreports.com tweaks or UNIX and Windows TCP/IP tuning tips.
You can find the Web100 variables descriptions gathered on the following web page.
A list of servers known to the Researh and Education Network (REN) community is located on the Internet2 e2epi web page. Note: that not all of these REN servers will be publicly accesible.
You can see the hops (routers) that your packets pass through from your machine to a target Internet site with the traceroute command (for Windows, use tracert in DOS/command prompt window). The route can actually vary from packet to packet, test to test, and the reverse route (return path) may not be the same. There are several traceroute servers around the world that can show you the route back to your browser. Tom Dunigan at ORNL also has traceroute servers at ORNL and at UT.
The NDT server window size for this Java tester is 64KB. Max window used to be 64KB, but newer OS's now support window scaling, so you may be able to request more than 64 KB. (This NDT server a window of 64,000 bytes, and the network interface is 100 Mbs.)
The NDT software (source and compiled programs) is available via the Internet2 End2End Performance Initiative web server at e2epi.internet2.edu/ndt/download.html. You can also learn more about the NDT system by subscribing to the NDT user discussion or NDT announcement lists hosted by Internet2.
This java applet was originally developed by ORNL and has been extensively modified
Complete University of Chicago Copyright Notice