home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
X-Original-To: nanog@nanog.org Date: Tue, 6 Dec 2016 20:45:11 -0500 From: "Mike O'Connor" <mjo@dojo.mi.org> To: North American Network Operators Group <nanog@nanog.org> In-Reply-To: <fe770d0c-bbf8-ec62-32b1-b61e3152bcee@gmail.com> Errors-To: nanog-bounces@nanog.org --fagq6euvypvsmz7p Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable :On 05-12-2016 16:34, Nick Ryce wrote: :> For testing downloads, fast.com is pretty nice :>=20 : :The problem with fast.com is that they use HTTPS for the test. The user ne= eds :a fast computer to decode the SSL at full speed. Even if you have a very f= ast :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@dojo.mi.o= rg =3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D= =3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D--=3D=3D= --=3D "A superhero should always speak from his diaphragm!" -The Ti= ck --fagq6euvypvsmz7p Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQBVAwUBWEdpp5Eu6kwgW799AQKFrQH+JiJf0GZ4LUTze2eQRGhKjXomP7C20DvG elsQM3lgJv27W5tnRlrRVUfhVP+1j2FumUCrDb8V/0EnaWgdTYiyhQ== =1Yf6 -----END PGP SIGNATURE----- --fagq6euvypvsmz7p--
home | help | back | first | fref | pref | prev | next | nref | lref | last | post |