From: Jeremy Marks <jmarks@uchicago.edu>
To: "flent-users@flent.org" <flent-users@flent.org>
Subject: [Flent-users] interpreting my RRUL results
Date: Tue, 16 Jun 2020 17:58:05 +0000 [thread overview]
Message-ID: <DM6PR11MB4154AABFFC6E05BAA1405431B19D0@DM6PR11MB4154.namprd11.prod.outlook.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1053 bytes --]
This rrul test was run in a Linux Mint VM on a computer directly connected to my Arris BGW210 DSL modem, carrying my AT&T provided service at 75/20.
My original plan was to analyze buffer bloat from machines behind my router that is behind this modem, in case my performance would increase with a Ubiquiti Edgerouter that supports shaping algorithms such as cake.
However, I thought I had better first see what impact the modem itself has on the buffer bloat situation.
Below is the standard unscaled triple plot from rrul. It looks pretty awful to me, but I am not experienced in reading these.
I would be grateful for help in interpreting these graphs, and for any suggestions on what, if anything, I can do (buy an IQrouter, perhaps)?
Also, I would imagine that, the best I could do with a traffic shaping secondary router would be to not make things any worse. Would that be correct?
Many thanks for any education and thoughts about what to do next.
JM
[A close up of a map Description automatically generated]
jm
[-- Attachment #1.1.2: Type: text/html, Size: 3826 bytes --]
[-- Attachment #1.2: image002.jpg --]
[-- Type: image/jpeg, Size: 76176 bytes --]
[-- Attachment #2: Type: text/plain, Size: 151 bytes --]
_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org
reply other threads:[~2020-06-16 17:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.flent.org/postorius/lists/flent-users.flent.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM6PR11MB4154AABFFC6E05BAA1405431B19D0@DM6PR11MB4154.namprd11.prod.outlook.com \
--to=jmarks@uchicago.edu \
--cc=flent-users@flent.org \
/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