From: Pete Heist <pete@heistp.net>
To: Cake List <cake@lists.bufferbloat.net>
Subject: [Cake] FreeNet backhaul
Date: Fri, 7 Sep 2018 00:37:43 +0200 [thread overview]
Message-ID: <2CB335A2-E18F-430F-9331-9AD9B3238D84@heistp.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
I met with the FreeNet Liberec admins earlier this week, and am just starting to get the first IRTT / SmokePing probe data from a few backhaul routers. I’ll see if I can get snapshots of the SmokePing pages public somewhere, but for now...
https://www.heistp.net/downloads/jerab_ping.pdf <https://www.heistp.net/downloads/jerab_ping.pdf>
https://www.heistp.net/downloads/jerab_irtt.pdf <https://www.heistp.net/downloads/jerab_irtt.pdf>
On this router, there are various “events” that occur with RTT spikes, and in general, UDP RTT maximums appear quite a bit higher than those for ICMP. I speculate that at least some of these events may be bloat, but can’t be sure yet.
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.
I feel the need for better data than this, but this is at least a first look for me at bloat in an ISP’s backhaul. The “elaborate” plan is to gather data for a while, deploy sqm in a couple places (I hope for cake, but the kernel will need to be upgraded on this one), and see what happens… :)
Pete
[-- Attachment #2: Type: text/html, Size: 1864 bytes --]
next reply other threads:[~2018-09-06 22:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 22:37 Pete Heist [this message]
2018-09-06 22:58 ` Dave Taht
2018-09-06 23:03 ` Jonathan Morton
2018-09-07 10:00 ` Pete Heist
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=2CB335A2-E18F-430F-9331-9AD9B3238D84@heistp.net \
--to=pete@heistp.net \
--cc=cake@lists.bufferbloat.net \
/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