General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Jim Gettys <jg@freedesktop.org>
Cc: bloat <bloat@lists.bufferbloat.net>,
	"aqm@ietf.org" <aqm@ietf.org>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Bloat] [aqm] the side effects of 330ms lag in the real world
Date: Tue, 29 Apr 2014 19:01:36 +0200	[thread overview]
Message-ID: <87bnvkkr2n.fsf@toke.dk> (raw)
In-Reply-To: <CAGhGL2Bzo1Jmq0Tu2t-3w+2m4Sy7BpOkBQE-_C3vAg75JZR=2w@mail.gmail.com> (Jim Gettys's message of "Tue, 29 Apr 2014 12:44:38 -0400")

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

Jim Gettys <jg@freedesktop.org> writes:

> Now, if someone gives me real fiber to the home, with a real switch fabric
> upstream, rather than gpon life might be somewhat better (if the switches aren't
> themselves overbuffered.... But so far, it isn't.

As a data point for this, I have fibre to my apartment building and
ethernet into the apartment. I get .5 ms to my upstream gateway and
about 6 ms to Google. Still measured up to ~20 ms of bufferbloat while
running at 100 Mbps...

http://files.toke.dk/bufferbloat/data/karlstad/cdf_comparison.png

However, as that graph shows, it is quite possible to completely avoid
bufferbloat by deploying the right shaping. And in that case fibre
*does* have a significant latency advantage. The best latency I've seen
to the upstream gateway on DSL has been ~12 ms.

-Toke

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]

  parent reply	other threads:[~2014-04-29 17:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29  1:24 [Bloat] " Dave Taht
2014-04-29  7:08 ` [Bloat] [aqm] " Mikael Abrahamsson
2014-04-29  7:21   ` Fred Baker (fred)
2014-04-29  7:56     ` Mikael Abrahamsson
2014-04-29 15:46       ` Dave Taht
2014-04-29 16:51         ` Aaron Wood
2014-04-29 16:44       ` Jim Gettys
2014-04-29 16:57         ` Jim Gettys
2014-04-29 17:01         ` Toke Høiland-Jørgensen [this message]
2014-04-29 17:07           ` Jim Gettys
2014-04-29 18:09             ` Greg White
2014-04-30  3:21           ` Dave Taht
2014-04-30  6:53           ` Jan Ceuleers
2014-04-30  8:19             ` Pedro Tumusok
2014-04-30  8:30             ` Mikael Abrahamsson
2014-04-29 17:02         ` Dave Taht
2014-04-30  6:16         ` Mikael Abrahamsson
2014-04-29  7:43   ` Tristan Seligmann
2014-04-29 23:01 Hal Murray
2014-04-29 23:26 Michael Spacefalcon
2014-04-29 23:56 ` Steinar H. Gunderson
2014-04-30  0:14 ` Hal Murray

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=87bnvkkr2n.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=aqm@ietf.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=jg@freedesktop.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