General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Cc: "Håvard Staub Nyhus" <hnyhus@gmail.com>,
	"Marius Hole" <hole@gathering.org>
Subject: [Bloat] latency looks good again at the gathering
Date: Thu, 28 Mar 2013 16:05:19 -0700	[thread overview]
Message-ID: <CAA93jw7WuRLd=LC4ZEzB2qotUhfxJSe-B9hymj7dEWYphPchsg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]

Bloat list:

I note that yesterday's problem with the long period latency swings was
narrowed down to a bad card or connector in the chassis, and that fiber
connection has been disabled.

I've got packet captures covering a goodly percentage of the universe now
(thanks to the hard work of the cc'd).... and occasionally I do things like
checking ipv6 vs ipv4 performance going internationally so as to have a
reference later.

http://gathering-edge.bufferbloat.net/~d/california/california_46compete-3.svg

Interesting about the ping part of the plot - there seems to be some
classification on the link, and it's neat
that BE traffic stops (packet loss there), that the EF traffic has got a
different RTT than the BK (CS1) traffic (which is the lowest latency of the
bunch!!!) , and that ipv6 has lower latency than ipv4 on this path(s). (duh)

as for the periodic bits of long period TCP changes, darned if I know...
that's what I have packet captures for.

you can see some sort of major packet loss event at T+168 or so here:

http://gathering-edge.bufferbloat.net/~d/california/california_46compete-long-3.svg

As to where it occurred, well, darn it,  "mtr" was part of the rrul spec
and haven't got around to integrating it.

Anyway, another long period 6vs4

http://gathering-edge.bufferbloat.net/~d/california/california_46compete-long-600.svg


-- 
Dave Täht

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

[-- Attachment #2: Type: text/html, Size: 1972 bytes --]

                 reply	other threads:[~2013-03-28 23:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAA93jw7WuRLd=LC4ZEzB2qotUhfxJSe-B9hymj7dEWYphPchsg@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=hnyhus@gmail.com \
    --cc=hole@gathering.org \
    /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