Favorite Speed Test Systems

Mike O'Connor mjo at dojo.mi.org
Wed Dec 7 01:45:11 UTC 2016


:On 05-12-2016 16:34, Nick Ryce wrote:
:> For testing downloads, fast.com is pretty nice
:> 
:
:The problem with fast.com is that they use HTTPS for the test. The user needs
:a fast computer to decode the SSL at full speed. Even if you have a very fast
:computer the test will max out at 100-200 Mbps because the Netflix servers
:are apparently not able to encode SSL any faster. Maybe we would get better
:speed if multiple SSL connections were used.

I've run into the opposite problem -- fast.com sporadically reporting
1+ Gbps times for circuits that are only 20-40 Mbps.  There's no obvious
client-side issues -- no proxying, interesting browsers, etc.  fast.com
is glitchy just often enough to give some friends of mine silly glee
when it misreports.

-Mike

--
 Michael J. O'Connor                                          mjo at dojo.mi.org
 =--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--=
"A superhero should always speak from his diaphragm!"               -The Tick
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20161206/7bb73f61/attachment.pgp>


More information about the NANOG mailing list