From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <bloat@lists.bufferbloat.net>
Subject: [Bloat] Remarkably simple bloat managing use by a UK ISP
Date: Fri, 5 Jun 2015 15:46:14 +0100 [thread overview]
Message-ID: <5571B636.8050908@darbyshire-bryant.me.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 460 bytes --]
Hi Chaps,
I was speaking with Andrews & Arnold (a UK clueful ISP) about their
experiences with bufferbloat and was sent this graph:
https://support.aa.net.uk/VMG1312:_QoS
I was surprised at how such a simple 'priority by packet size' scheme
appears to work. Clearly there's slightly more going on in that the box
in question *knows* the outbound bandwidth and doesn't let a standing
queue form...but priority by packet size? Hmm.
Kevin
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4791 bytes --]
next reply other threads:[~2015-06-05 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 14:46 Kevin Darbyshire-Bryant [this message]
2015-06-05 15:50 ` Dave Taht
2015-06-05 16:35 ` Jonathan Morton
2015-06-05 16:46 ` Dave Taht
2015-06-05 16:59 ` Jonathan Morton
2015-06-05 17:39 ` Sebastian Moeller
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=5571B636.8050908@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--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