Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
* [Starlink] plotting all the data
@ 2021-06-17 13:56 Dave Taht
  2021-06-17 14:24 ` Nick Buraglio
  0 siblings, 1 reply; 5+ messages in thread
From: Dave Taht @ 2021-06-17 13:56 UTC (permalink / raw)
  To: starlink; +Cc: Matt Mathis

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….


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2021-06-17 20:18 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-17 13:56 [Starlink] plotting all the data Dave Taht
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox