From: Nathan Owens <nathan@nathan.io>
To: George Burdell <gb@teklibre.net>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Open Data
Date: Wed, 9 Jun 2021 12:48:58 -0700 [thread overview]
Message-ID: <CALjsLJvfXWV2w9yjQ31ooKCXn6KUDraPKFj6U0DHfsMb4-BAaA@mail.gmail.com> (raw)
In-Reply-To: <20210609173526.GA17949@mail.taht.net>
[-- Attachment #1.1: Type: text/plain, Size: 1288 bytes --]
[image: rtt-tcp_1up_-_1-flow-fq_starlink_noecn-sqm-cc=cubic.png]
I'm new to the flent things -- but in this test, what was CAKE configured
to use for bandwidth? Based on the other graph maybe 5-10Mbps?
On Wed, Jun 9, 2021 at 10:35 AM George Burdell <gb@teklibre.net> wrote:
> For those new around here, bufferbloat.net project members have
> always believed in open code and open data. Been a bit coy this
> month... but... for your research....
>
> All the data collected so far (flent and packet captures)
> is available via rsync to these git repositories, and we consider
> to be "public", just distributed via an older means called rsync.
>
> mkdir starlink; cd starlink; rsync -av fremont.starlink.taht.net::starlink
> .
> cd ..; mkdir starlink_cap; rsync -av fremont.starlink.taht.net::starlink_cap
> .
>
> See the git logbook for pithy details.
>
> Useful things to extract from this data are tons of flent comparison
> plots and from the packet captures, interrarrival times, loss
> and ecn markings. And who knows what else.
>
> All the tests can be easily repeated from anywhere, full source code is
> provided.
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #1.2: Type: text/html, Size: 2088 bytes --]
[-- Attachment #2: rtt-tcp_1up_-_1-flow-fq_starlink_noecn-sqm-cc=cubic.png --]
[-- Type: image/png, Size: 96319 bytes --]
prev parent reply other threads:[~2021-06-09 19:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 17:35 George Burdell
2021-06-09 19:48 ` Nathan Owens [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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALjsLJvfXWV2w9yjQ31ooKCXn6KUDraPKFj6U0DHfsMb4-BAaA@mail.gmail.com \
--to=nathan@nathan.io \
--cc=gb@teklibre.net \
--cc=starlink@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