General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Adrian Kennard <a@k.gg>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Bloat goes away, but with ~25% speed loss?
Date: Fri, 5 Jun 2015 10:48:41 -0700	[thread overview]
Message-ID: <CAA93jw5dRkFUcTuhO1FN5vtDXcrEMO+cASwk8DV28a+Dzc=4mg@mail.gmail.com> (raw)
In-Reply-To: <5571DC01.70301@k.gg>

On Fri, Jun 5, 2015 at 10:27 AM, Adrian Kennard <a@k.gg> wrote:
> On 05/06/2015 18:23, Dave Taht wrote:
>>>> A&A struck me as an extremely clueful ISP (I think they have had ipv6
>>>> /48s for forever?)
>>>> and it has been my impression that folk like that were using things
>>>> like HFSC + SFQ already
>>>> in their "rate limiters", and had experimented also with fq_codel by now.
>
> Oh, I meant to say, the policers used on broadband links have a very
> very simple logic of small packets (<1000) are allowed more predicted
> lag, and so VoIP "just works" as does DNS, interactive key presses, TCP
> ACK packets and all sorts of time critical stuff.

Yes, I have thought about many improvements to the linux based policer
with "bobbie", including this one.

Still, prior to running out of cpu with inbound shaping + fq_codel on
the cpe side, we were doing so well that I basically figured that the
same stuff was also very applicable to the isp's side, particularly as
we approached higher rates.

Matt Mathis is always whinging about bad policer implementations
showing up in the google mlabs datasets... certainly linux's is
insanely primitive even compared to the rfcs.

So I am curious as to how well A&A's AS20712 (?) clients are doing on
the new dslreports.com/speedtest, which shows the "bloat" grade and
actual behavior over time?

And I think dslreports is now publishing summary statistics somewhere??

 shibbolet!

-- 
Dave Täht
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast

  parent reply	other threads:[~2015-06-05 17:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 21:18 Rich Brown
2015-06-04 20:01 ` Jonathan Morton
2015-06-05 14:33   ` Kevin Darbyshire-Bryant
2015-06-05 16:19     ` Dave Taht
2015-06-05 17:20       ` Kevin Darbyshire-Bryant
2015-06-05 17:23         ` Dave Taht
2015-06-05 17:25           ` Adrian Kennard
2015-06-05 17:27           ` Adrian Kennard
2015-06-05 17:44             ` Kevin Darbyshire-Bryant
2015-06-05 17:48             ` Dave Taht [this message]
2015-06-05 17:51               ` Adrian Kennard
2015-06-05 17:57                 ` Kevin Darbyshire-Bryant
2015-06-05 17:59                   ` Adrian Kennard
2015-06-05 19:44                     ` Dave Taht
2015-06-05 20:06                       ` Dave Taht
2015-06-05 22:45                         ` jb
2015-06-05 22:52                           ` Dave Taht
     [not found]                           ` <55722786.7090904@hp.com>
2015-06-06  0:32                             ` jb
2015-06-06  0:40                               ` Rick Jones
2015-06-06  3:54                         ` Aaron Wood
2015-06-06  4:13                           ` jb
2015-06-06  8:45                         ` Kevin Darbyshire-Bryant
2015-06-06  9:30                           ` jb
2015-06-06 10:04                             ` Kevin Darbyshire-Bryant
2015-06-06 10:22                               ` jb
2015-06-04 23:32 ` Aaron Wood
2015-06-04 23:38 ` Rick Jones

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='CAA93jw5dRkFUcTuhO1FN5vtDXcrEMO+cASwk8DV28a+Dzc=4mg@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=a@k.gg \
    --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