Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "David P. Reed" <dpreed@deepplum.com>
To: "Kevin Darbyshire-Bryant" <kevin@darbyshire-bryant.me.uk>
Cc: "Jonathan Morton" <chromatix99@gmail.com>,
	"Cake List" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Cake tin behaviour - discuss....
Date: Sun, 26 Apr 2020 09:53:47 -0400 (EDT)	[thread overview]
Message-ID: <1587909227.334329276@apps.rackspace.com> (raw)
In-Reply-To: <0AA356B0-AC91-4F4E-94A6-184C3E090FCA@darbyshire-bryant.me.uk>

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


Very interesting. However, I'm curious about what is being "ping'ed" from outside.
 
I would bet that the ping comes in on your router interface and is reflected immediately back. Which would mean that it might not at all be going through the Cake layer. That depends on the details of your setup, which you didn't share.
 
As you probably know, Cake works by packet shaping in the box where it runs, in the Linux stack. If the ping responder is on the ISP side of Cake, it will not be measuring lag-under-load *inside* cake.
 
End-to-end lag-under-load on multiple paths sharing a bottleneck is the problem Cake was invented to solve. (Jonathan - you agree?) Yes, it will move that congestion "inside" itself, pulling it out of the bottleneck itself. There it drops and ECN's "as if" the bottleneck were working correctly, rather than being "bufferbloated".
 
So it would be interesting to learn more about the topology of your test to interpret this ping.  A more interesting ping would be along the fujl path that the other flows are taking. Your ISP can't provide that.
 
 
On Saturday, April 25, 2020 5:31pm, "Kevin Darbyshire-Bryant" <kevin@darbyshire-bryant.me.uk> said:



> 
> 
> > On 25 Apr 2020, at 21:56, David P. Reed <dpreed@deepplum.com> wrote:
> >
> > Question: what's the "lag under load" experienced when these two loads are
> filling the capacity of the bottleneck router (the DSL link)?
> > I'm wondering whether your cake setup is deliberately building up a big queue
> within the router for any of the 10 bulk/best efforts flows.
> 
> https://www.thinkbroadband.com/broadband/monitoring/quality/share/3dec809ecef5cd52f574b6be5da9af28326845d6-25-04-2020
> 
> I don’t reckon it’s bad for the past 24 hours, one peak at 50ms. Avg
> latency increase by about 6ms during load.
> 
> 
> 

[-- Attachment #2: Type: text/html, Size: 3359 bytes --]

  reply	other threads:[~2020-04-26 13:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-25 11:07 Kevin Darbyshire-Bryant
2020-04-25 15:14 ` David P. Reed
2020-04-25 15:25 ` Jonathan Morton
2020-04-25 20:34   ` Kevin Darbyshire-Bryant
2020-04-25 20:56     ` David P. Reed
2020-04-25 21:31       ` Kevin Darbyshire-Bryant
2020-04-26 13:53         ` David P. Reed [this message]
2020-04-27 11:52           ` Kevin Darbyshire-Bryant

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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1587909227.334329276@apps.rackspace.com \
    --to=dpreed@deepplum.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=kevin@darbyshire-bryant.me.uk \
    /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