General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Jonathan Morton <chromatix99@gmail.com>, "Livingood\,
	Jason" <Jason_Livingood@comcast.com>,
	"bloat\@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] AQM & Net Neutrality
Date: Mon, 24 May 2021 17:13:40 -0400	[thread overview]
Message-ID: <32011.1621890820@localhost> (raw)
In-Reply-To: <9CDBF19A-C131-4497-9456-285343F93787@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1949 bytes --]


Jonathan Morton <chromatix99@gmail.com> wrote:
    > I'm pleased to help with education in this area.  The short and
    > simplistic answer would be that AQM treats all traffic going through it
    > equally; the non-interactive traffic *also* sees a reduction in
    > latency; though many people won't viscerally notice this, they can
    > observe it if they look closely.  More importantly, it's not necessary
    > for traffic to make any sort of business or authentication arrangement
    > in order to benefit from AQM, only comply with existing,
    > well-established specifications as they already do.

    > If the traffic supports ECN, the AQM can use that instead of packet
    > drops for signalling, which tends to actually *reduce* packet loss in
    > bulk transfers, compared to simply bouncing off the tail end of a dumb
    > FIFO.  Reduced latency would already make recovering from these losses
    > easier for the transport, but eliminating them entirely means that the
    > application receives a completely smooth delivery, with no sudden
    > pauses and jumps caused by the recovery process.

So it seems that it be fair to say that by reducing the latency, and finding a more
reasonable bandwidth*delay value, the AQM allows non-interactive traffic to
make do with less buffering.  This improves memory utilitization on the
receiver (the viewer), but perhaps more importantly, might it also improve
memory ultilization on the sender by allowing sent data to be purged faster.

Could this reduce the cost of OTT streaming services?
Maybe the savings is insignificant for a small service, but could it be
substantial for larger services?  (there is a media spin to avoid here)

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2021-05-24 21:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 13:09 Livingood, Jason
2021-05-24 14:30 ` Jonathan Morton
2021-05-24 14:51   ` Jonathan Morton
2021-05-24 21:13   ` Michael Richardson [this message]
2021-05-24 19:18 ` Stuart Cheshire
2021-05-24 21:23   ` Michael Richardson
2021-05-25 16:03   ` Jonathan Morton
2021-05-26 18:32     ` Dave Taht
2021-05-26 18:36       ` Dave Taht
2021-05-28 22:28         ` Aaron Wood
2021-05-28 23:18           ` Sebastian Moeller
2021-06-03  9:23   ` Holland, Jake

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=32011.1621890820@localhost \
    --to=mcr@sandelman.ca \
    --cc=Jason_Livingood@comcast.com \
    --cc=bloat@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