[190716] in North American Network Operators' Group
RE: I recommend dslreports.com/speedtest these days (was
daemon@ATHENA.MIT.EDU (Eric Tykwinski)
Fri Jul 22 15:43:04 2016
X-Original-To: nanog@nanog.org
From: "Eric Tykwinski" <eric-list@truenet.com>
To: "'nanog list'" <nanog@nanog.org>
In-Reply-To: <CAGhGL2Bm1WuCWVZzqxhBS7jWFn1ws_x=Wz2sZoEf1Kd9+9pH7A@mail.gmail.com>
Date: Fri, 22 Jul 2016 15:42:49 -0400
Errors-To: nanog-bounces@nanog.org
Jim,
No problems, I just knew you were one of the project founders. I found =
it on the website shortly after posting.
My google-fu wasn=E2=80=99t up to par.
https://www.bufferbloat.net/projects/cerowrt/wiki/Tests_for_Bufferbloat/
I=E2=80=99m assuming I used the script last time for netperf, but have =
downloaded Flent to give it a shot.
Sincerely,
Eric Tykwinski
TrueNet, Inc.
P: 610-429-8300
_________________________________________________________________________=
_________________
From: gettysjim@gmail.com [mailto:gettysjim@gmail.com] On Behalf Of Jim =
Gettys
Sent: Friday, July 22, 2016 3:23 PM
To: Eric Tykwinski
Cc: nanog list; jb; Toke H=C3=B8iland-J=C3=B8rgensen; Dave Taht
Subject: Re: I recommend dslreports.com/speedtest these days (was =
Speedtest.net not accessible in Chrome due to deceptive ads)
I don't read this list continually, but do archive it; your note was =
flagged for me to comment on.
On Thu, Jul 21, 2016 at 8:11 PM, Eric Tykwinski <eric-list@truenet.com> =
wrote:
This is probably for Jim Gettys directly, but I=E2=80=99m sure most =
others have input. I could of sworn that that there was some test made =
to detect it directly on switches and routers? Sort of like iperf, but =
to test bufferbloat specifically given the OS stack which is going to =
have issues as well, as shown on bufferbloat.net =
<http://bufferbloat.net/>.
=E2=80=8BWe recommend Toke H=C3=B8iland-J=C3=B8rgensen's
=E2=80=8B
"flent" =E2=80=8B
=20
=E2=80=8Bhttps://flent.org/ for testing connections/devices/gear. It =
uses "netperf" transfers to load the link (by default with 4 =
simultaneous TCP connections in both directions, IIRC), and then runs =
another test (by default "ping") at the same time to test the connection =
under load.=20
Turning on a netperf server is just as easy as turning on an iperf =
server (and the results are better, and netperf's maintainer =
responsive).=E2=80=8B
See the documentation/paper on Toke's web site. The "RRUL" test=20
("Real-Time Response Under Load") is the one we use most/is best shaken =
down. I'm sure Toke would love help with other tests.
=E2=80=8B
Gives you lots of useful graphs, will do diffserv marking, =
etc...=E2=80=8B
