General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Robinson,
	Andrew 1. (NSN - US/Mountain View)" <andrew.1.robinson@nsn.com>
Cc: "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Bufferbloat in local networks...
Date: Mon, 22 Jul 2013 15:42:47 -0700	[thread overview]
Message-ID: <CAA93jw7vzckKS=Eg=cBqR=uAuZ1Cq_bGGru6wqnSMhHB72iVqg@mail.gmail.com> (raw)
In-Reply-To: <AB6106518A3C594881435A2349935C9C04D3F8@USCHMBX003.nsn-intra.net>

On Mon, Jul 22, 2013 at 3:34 PM, Robinson, Andrew 1. (NSN -
US/Mountain View) <andrew.1.robinson@nsn.com> wrote:
> Hi,
>
> Are there any tools to measure bufferbloat in local networks?

The most popular tool for local networks at this point is
netperf-wrapper's partial implementation of the rrul test suite.

https://github.com/tohojo/netperf-wrapper

It only implements about 1/3 of the specification at the moment, but
it, when also run with tools like mtr, are helpful for identifying
sources of bufferbloat on a local network, if you find any. It is
dependent on a recent version of netperf (2.6 or later) being
installed on client and server.

One misleading thing about the current rrul benchmarks is that it uses
ping rather than one way delay measurements, and that the udp traffic
generated stops after one loss. What I'd wanted was to be measuring
against an isochronous stream rather than something that scaled
geometrically with RTT.

On that front I have been evaluating owamp's methods and code (in the
hope of coming up with something simpler), but so far that's the
winner for creating and measuring one way delay and simulating voip
and gaming traffic.

http://www.internet2.edu/performance/owamp/

Most of my talks use the rrul suite in some way or another, although I
think I've been making a mistake in almost always presenting the 8
stream benchmark (I use the single stream stuff a lot)...


>
> Thanks,
> Andrew
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

      reply	other threads:[~2013-07-22 22:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 22:34 Robinson, Andrew 1. (NSN - US/Mountain View)
2013-07-22 22:42 ` Dave Taht [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw7vzckKS=Eg=cBqR=uAuZ1Cq_bGGru6wqnSMhHB72iVqg@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=andrew.1.robinson@nsn.com \
    --cc=bloat@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox