Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] qos calculator & paper for htb rate selection
Date: Sat, 18 Jun 2016 21:20:00 -0700	[thread overview]
Message-ID: <CAA93jw7cHjKhoZ+JW+9XTT1x12HUj0ETjWxKXhWyr4EzwHxTqg@mail.gmail.com> (raw)
In-Reply-To: <480A221C-E51E-4A77-A0DA-105DD2E0E427@gmail.com>

I liked the question they tried to answer, if not their results. :)

As I push a downstream shaper closer to 95% I have been able to get to
where there is sufficient buffering one hop away to where it takes 10s
of seconds or forever for an aqm to drain the result. Your efforts
towards measuring smoothness seemed like a partial start to having
some other trigger to get back minimum queuing, but not quite.

The fact that the 85% number is essentially folklore rather than
science is bothersome. I've spent a lot of time over the last 5 years
researching various models, queue theories, statistical distributions,
and so on, and don't feel like I'm any further better off than I was
when I started. There's always things that look promising (see, for
example "hopf bifurcation" for something I'm trying to understand
currently), other things like alternate statistical distribution
methods, which seem to show a tantalizing hint of working, and they
always peter out...

There are a lot of people that believe in policers, also, and I have
had such bad results with those as to give up. It would be nice to
*prove* that policers didn't work or establish the bounds of their
range, also.

I go back and I read how clearly understood some things could be back
in the 90s, and I envy those people - but I imagine those things were
just as confusing at the time those papers were being written as clear
as they may now seem.

Another paper "sticking with me is:"

https://plus.google.com/u/0/107942175615993706558/posts/gC6oahMETvr

and yet:

This is the best book on bloat I've read yet:
https://plus.google.com/u/0/107942175615993706558/posts/adye5CKrPMF

  reply	other threads:[~2016-06-19  4:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-19  0:53 Dave Taht
2016-06-19  3:43 ` Jonathan Morton
2016-06-19  4:20   ` Dave Taht [this message]
2016-06-19 18:37 ` moeller0

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/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=CAA93jw7cHjKhoZ+JW+9XTT1x12HUj0ETjWxKXhWyr4EzwHxTqg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    /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