As mentioned, there is a limitation to TCP-based speed tests - TCP throughput
is very sensitive to packet losses, particularly during slow-start, in addition
to requiring end-host tuning (as an exercise, try running speedtest.net on a
high bandwidth connection). You could use something called "available
bandwidth", which is kind of like the "leftover capacity" on your path - I've
been using this tool called pathload2:
http://www.measurementlab.net/measurement-lab-tools#pathload2
_________________________________________________________________
Keep your friends updated—even when you’re not signed in.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_5:092010
