Jab-Diddle

But, any satellite based user will have a minimum of some 600 ms lost to latency, and which can increase during primetime...if satellite user's "proxy server" is located in same city as the test server...if not, latency increases as a function of distance from test server location. Hence, unless a test site accounts for user's latency (not proxy server's latency), then results will be skewed much more on smaller sized test loads than on larger sized tests. Hence, if a test site is using bytes/time formula without latency factored in, then inacurrate accounting.

On Exede satellite service, I noticed a pattern to this user's results. When this user uses a 10 MB or larger test file, his results are like 6.8 Mbps to 20.08 Mbps. But, when he uses a 1 MB or less test file, his results vary from 54 kbps to 582 Kbps. Both Hughes and Exede use a proxy to fetch, and I have seen erroueous results from Testmy, and other testing sites. It would appear Testmy's results may not be the real thing, from time to time.

Via satellite, latency is longer than land-line broadband [Cable, DSL] or even Wireless [WISP]. Latency runs around 600-900ms on average for most satellite users.