From: Jonathan Morton <chromatix99@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake strange behaviour
Date: Sat, 16 Jul 2016 19:25:10 +0300 [thread overview]
Message-ID: <C0336D18-E37D-44AF-956A-8E318F8DD7F5@gmail.com> (raw)
In-Reply-To: <5789FFEF.9010408@darbyshire-bryant.me.uk>
> Line is a 40/10 cake limited to 39000/9840.
I think you might be rather optimistic on your ingress shaping rate. In order to control the queue effectively in the (less ideal) downstream position, the shaper needs to be set somewhat below the actual line rate. I’m not yet sure exactly how far down it needs to be, but just 2.5% is probably not enough, especially in the face of a traffic type reputed to be “intensive".
> Without extensive testing I have no faith that the current aqm implementation in cake is actually working.
Meanwhile, I’ve been downloading a fresh copy of Star Citizen for the past 12+ hours, using the extremely intensive P2P method. Cake reported 300-500 *bulk* flows at various times, all in the Best Effort tin. Web browsing on the same machine is predictably slow, but actually works (aside from servers which automatically cut connections after a timeout, even if they aren’t idle).
But web browsing on a *different* machine is still responsive, even with fairly large images, thanks to triple-isolation. That wouldn’t happen unless the upstream queue was being kept empty - a very difficult task under that sort of load.
All this is greatly helped by the fact that my 3G ISP has apparently just upgraded a nearby tower, so I am now able to set 4Mbps ingress without having to account for a lot of variability. Previously I had to set 1Mbps ingress to be sure of low latencies.
I really should get on with migrating my firewall to a different box, to free up the one with two NICs. Then I can run the sort of tests that might actually convince people.
- Jonathan Morton
prev parent reply other threads:[~2016-07-16 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-16 9:35 Kevin Darbyshire-Bryant
2016-07-16 10:59 ` Dave Täht
2016-07-16 11:53 ` Kevin Darbyshire-Bryant
2016-07-16 12:44 ` Dave Täht
2016-07-16 13:37 ` Sebastian Moeller
2016-07-16 16:25 ` Jonathan Morton [this message]
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=C0336D18-E37D-44AF-956A-8E318F8DD7F5@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--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