From: Jonathan Morton <chromatix99@gmail.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Bloat goes away, but with ~25% speed loss?
Date: Thu, 4 Jun 2015 23:01:46 +0300 [thread overview]
Message-ID: <CAJq5cE0DYBt9nGAFk6EHezakDrvwS=1hLGg31HLxx0WQ+EvRww@mail.gmail.com> (raw)
In-Reply-To: <7D4DDC3F-9233-4E07-B59B-AA1368CA9D4E@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]
I think he may be seeing a complex interaction of various different queue
components and bottlenecks, which in total manages to confuse TCP
congestion control sufficiently to cause reduced throughput.
I suspect that there is a shaper at the ISP end which limits the bandwidth
available to any single subscriber. This is separate from the queue serving
the tower itself, which is what has been admitted to be periodically
overloaded. However, "overloaded" in network engineer parlance just means a
multi-user link that is saturated. There might well be enough elasticity to
allow one subscriber their full allocation by pushing others out of the
way. In this condition, the tower queue will be full and so will the shaper
queue. I imagine the shaper queue contributes the most to induced latency.
However, this "pushing others out of the way" on a drop-tail queue is done
by allowing the congestion window to grow to large values, facilitated by
the deep ISP shaper queue. This effect is defeated (by design) by running
an ingress AQM shaper, which keeps the ISP shaper queue empty.
A useful exercise might be to log the idle latency over a long period of
time, and correlate it to peak load periods, as A&A do.
http://aa.net.uk/kb-broadband-cqm.html .
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 1443 bytes --]
next prev parent reply other threads:[~2015-06-04 20:01 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 [this message]
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
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='CAJq5cE0DYBt9nGAFk6EHezakDrvwS=1hLGg31HLxx0WQ+EvRww@mail.gmail.com' \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@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