From: Mikael Abrahamsson <swmike@swm.pp.se>
To: dpreed@reed.com
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Ubiquiti QOS
Date: Mon, 26 May 2014 15:02:13 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1405261454070.29282@uplift.swm.pp.se> (raw)
In-Reply-To: <1401079740.21369945@apps.rackspace.com>
On Mon, 26 May 2014, dpreed@reed.com wrote:
> Len Kleinrock and his student proved that the "optimal" state for
> throughput in the internet is the 1-2 buffer case. It's easy to think
> this through...
Yes, but how do we achieve it?
If you signal congestion with very small buffer depth used, TCP will back
off and you will drain the buffer, meaning the link will be underutilized.
This is great from an interactive point of view, but not so much for
keeping the link used actually at capacity without incurring excessive
buffering latency?
So you would like to see ECN drop=1 markings on all packets as soon as
they're the 3rd (or deeper) packet in the buffer? Or if the packet doesn't
have ECN markings, you'd just drop it?
I doubt this will create a beneficial system for the end user, sounds like
it focuses too much on interactivity and too little on throughput.
I just don't buy your statement that adding buffers won't increase
throughput. If you're optimizing for throughput, then you let a single
session use 1 second of buffering, meaning you know for a fact that the
link is always going to be used at 100%. This totally kills interactivity,
but it's still more throughput efficient than having 2 packet deep
buffers, where you're very likely to drain these two packets and then have
no packets in the buffer, meaning the link will be underutilized.
So, I'd agree that a lot of the time you need very little buffers, but
stating you need a buffer of 2 packets deep regardless of speed, well, I
don't see how that would work.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2014-05-26 13:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 6:17 Dane Medic
2014-05-25 14:23 ` Valdis.Kletnieks
2014-05-25 15:42 ` Mikael Abrahamsson
2014-05-25 20:00 ` dpreed
2014-05-26 0:18 ` Mikael Abrahamsson
2014-05-26 4:49 ` dpreed
2014-05-26 13:02 ` Mikael Abrahamsson [this message]
2014-05-26 14:01 ` dpreed
2014-05-26 14:11 ` Mikael Abrahamsson
2014-05-26 15:31 ` David P. Reed
2014-05-27 21:19 ` David Lang
2014-05-27 22:00 ` Dave Taht
2014-05-27 23:27 ` David Lang
2014-05-28 2:12 ` Dave Taht
2014-05-28 3:21 ` David Lang
2014-05-28 15:52 ` dpreed
2014-05-28 16:34 ` David Lang
2014-05-27 15:23 ` Jim Gettys
2014-05-27 17:31 ` Dave Taht
2014-05-28 15:33 ` dpreed
2014-05-28 15:20 ` dpreed
2014-05-28 18:33 ` David Lang
2014-05-29 12:11 ` David P. Reed
2014-05-29 15:29 ` dpreed
2014-05-29 19:30 ` David Lang
2014-05-29 23:40 ` Michael Richardson
2014-05-30 0:32 ` David P. Reed
2014-05-30 0:36 ` Dave Taht
2014-05-25 18:39 ` Sebastian Moeller
2014-05-25 19:33 ` Dave Taht
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=alpine.DEB.2.02.1405261454070.29282@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@reed.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