From: Pete Heist <pete@heistp.net>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] FreeNet backhaul
Date: Fri, 7 Sep 2018 12:00:49 +0200 [thread overview]
Message-ID: <3BA06BE5-FBD2-4FC8-86BB-786679A66147@heistp.net> (raw)
In-Reply-To: <1CFBCFB1-AC8B-4172-A4EB-1CE65DE62EF6@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]
> On Sep 7, 2018, at 1:03 AM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> On 7 Sep, 2018, at 1:37 am, Pete Heist <pete@heistp.net> wrote:
>>
>> This router is an old ALIX with kernel 2.6.26, but on the other hand it does have hfsc + esfq (a variant of sfq with host fairness) deployed, so if it’s actually controlling the queue, one might suspect that sfq it could control inter-flow latency at least somewhat.
>
> ESFQ has two important faults: it doesn't explicitly control the length of individual queues (only tail-drops when a global limit is reached), and it suffers from hash collisions at the full "birthday problem" rate. So some of your measurement traffic is likely colliding with real traffic and suffering accordingly.
Ah, ok, that is important.
> That still makes ESFQ far better than a dumb FIFO.
I’ve heard tales of the way things were.
As a contrast, the router I’m on: https://www.heistp.net/downloads/vysina_ping.pdf <https://www.heistp.net/downloads/vysina_ping.pdf> The big difference here is this router’s uplink is licensed spectrum full-duplex 100Mbit, whereas Jerab from earlier is 5GHz WiFi (2x NSM5). The shift around June was an upgrade from ALIX to APU.
I haven’t seen evidence yet of backhaul links running at saturation for long periods. When I watch throughputs in real-time I do see pulses though that probably don't show up in the long-term MRTG throughput graphs. I wonder what queue lengths look like at millisecond resolution during these events.
[-- Attachment #2: Type: text/html, Size: 2389 bytes --]
next prev parent reply other threads:[~2018-09-07 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 22:37 Pete Heist
2018-09-06 22:58 ` Dave Taht
2018-09-06 23:03 ` Jonathan Morton
2018-09-07 10:00 ` Pete Heist [this message]
2018-09-07 13:59 ` Dave Taht
2018-09-07 16:02 ` Pete Heist
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=3BA06BE5-FBD2-4FC8-86BB-786679A66147@heistp.net \
--to=pete@heistp.net \
--cc=cake@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