From: Dave Taht <davet@teklibre.net>
To: starlink@lists.bufferbloat.net
Cc: Matt Mathis <mattmathis@google.com>
Subject: [Starlink] plotting all the data
Date: Thu, 17 Jun 2021 06:56:57 -0700 [thread overview]
Message-ID: <C17CB66C-5C11-4BFB-BFF6-E645CB74DE93@teklibre.net> (raw)
Capturing and plotting *all* the data is often revealing.
Sometimes plotting the data you are discarding (for what seems like sane reasons) is quite revealing. Saw this on slashdot this morning, it’s good...
https://www.newyorker.com/magazine/2021/06/21/when-graphs-are-a-matter-of-life-and-death
In the bufferbloat effort I’ve fought time and time again for folk to stop throwing out data above the 95 percentile, and at the very least plot everything they threw out to find patterns...
dslreports’ graphing tools, for example, throws out a ton of “outliers" … and the only reason why there is no data past 4 sec here, is that the test doesn’t run long enough.
http://www.dslreports.com/speedtest/results/bufferbloat?up=1
(been trying to get ahold of someone over there to buy their raw data for years now. They have the biggest - 8 years worth - collection)
mlabs has a similar data reduction issue that they haven’t got around to fixing.
And more recently we encountered a smoothing problem in wireshark that made a halt in packet processing look more like a normal tcp cwnd cut….
next reply other threads:[~2021-06-17 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 13:56 Dave Taht [this message]
2021-06-17 14:24 ` Nick Buraglio
2021-06-17 15:28 ` Dave Taht
2021-06-17 15:49 ` Matt Mathis
2021-06-17 20:18 ` George Burdell
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=C17CB66C-5C11-4BFB-BFF6-E645CB74DE93@teklibre.net \
--to=davet@teklibre.net \
--cc=mattmathis@google.com \
--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