|
|
|
|
|
|
|
|
|
|
|
 |
|
|
|
|
|
|
I’ve been doing some research on network diagnostic tools recently. Turns out the “End-to-End Performance Initiative” of Internet2 has already created something called Network Diagnostic Tool (see http://e2epi.internet2.edu/ndt/).
I decided to try it out. There’re two versions of their Windows client – Java-based and command-line. The latter requires cygwin to build and I couldn’t find any working links to built bins. The former required me to install the Java runtime on my Vista machine, but that ended up being totally painless (see one of the first links at http://www.java.com/en/download/manual.jsp)! If anyone at E2EPI is listening – please fix your links …
There are a number of public NDT servers, mostly scattered around the US, that host the Java version. I picked the one at the National Science Foundation (http://ciseweb100.cise-nsf.gov:7123) since it seemed to be the farthest away that was accessible at the time. Anyway, the tool runs for about 20 seconds and then returns tons of network statistics. Most of it boils down to a DSL speed test, and there are already tons of those available on the web, but there were still some interesting data:
TCP/Web100 Network Diagnostic Tool v5.2.1e
…
running 10s outbound test (client to server) . . . . . 327.68Kb/s
running 10s inbound test (server to client) . . . . . . 874.46kb/s
Your PC is connected to a Cable/DSL modem
…
Web100 reports the Round trip time = 364.34 msec; the Packet size = 1460 Bytes; and
No packet loss was observed.
This connection is receiver limited 87.62% of the time.
Increasing the current receive buffer (64.0 KB) will improve performance
This connection is network limited 12.34% of the time.
No Comments »
|
|
|
|
|
|
|
|
|
Leave a Reply