From: richard <richard@pacdat.net>
To: Steve Bauer <s_bauer@alum.mit.edu>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Usage Based Billing - It's All About Perceived Congestion
Date: Tue, 01 Mar 2011 08:01:50 -0800 [thread overview]
Message-ID: <1298995310.15371.77.camel@amd.pacdat.net> (raw)
In-Reply-To: <AANLkTik99TsxLqVUNAD3AFAX4c-BHxY1ZezzXG=EyONa@mail.gmail.com>
Hi Steve
thanks for the feedback.
I guess it comes down to how the various modems achieve "burst"
throughput - by buffering and draining, or by actually increasing the
allocation of bandwidth for a time.
I'll remove that piece until I have more information.
richard
On Tue, 2011-03-01 at 08:57 -0500, Steve Bauer wrote:
> On Mon, Feb 28, 2011 at 4:56 PM, richard <richard@pacdat.net> wrote:
> > The result is:
> > http://digital-rag.com/article.php/All-About-Perceived-Congestion-UBB
> > It's aimed at the public and non-technical so allow me a few missing
> > things in the explanations :)
>
> Hi Richard,
>
> You recommended to your readers:
>
> "You want to bug your ISP to turn off any/all "helper" buffering in
> your modem that purports to "increase upload speed for short periods"
> since this is buffering and part of the problem."
>
> I am assuming you intended that to apply to Powerboost. Based upon my
> understanding of various implementations of Powerboost,
> turning it off would *not* help with latency under load simply
> because the buffer sizes are fixed in today's cable modems.
>
> So these issues are orthogonal. There are certainly
> problems, but turning off Powerboost isn't part of the fix.
>
> Indeed, turning Powerboost off could make the problem worse. A
> buffer that would otherwise have drained if Powerboost was in effect,
> would be more likely to have a queue of packets sitting in it adding
> additional latency to later arrivals. Again, my key assumption is
> that disabling Powerboost simply doesn't change the buffer size.
>
> As always, happy to be proved wrong. :-)
>
> Thanks,
> Steve Bauer
> MIT
--
Richard C. Pitt Pacific Data Capture
rcpitt@pacdat.net 604-644-9265
http://digital-rag.com www.pacdat.net
PGP Fingerprint: FCEF 167D 151B 64C4 3333 57F0 4F18 AF98 9F59 DD73
prev parent reply other threads:[~2011-03-01 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 21:56 richard
2011-03-01 2:57 ` Henrique de Moraes Holschuh
2011-03-01 7:37 ` Jeremy Visser
2011-03-01 9:18 ` Ondřej Bílka
2011-03-01 9:33 ` Steve Davies
2011-03-02 8:20 ` Ondřej Bílka
2011-03-01 13:57 ` Steve Bauer
2011-03-01 15:36 ` Jim Gettys
2011-03-01 16:01 ` richard [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=1298995310.15371.77.camel@amd.pacdat.net \
--to=richard@pacdat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=s_bauer@alum.mit.edu \
/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