From: Robert McMahon <rjmcmahon@rjmcmahon.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Dave Taht via Rpm <rpm@lists.bufferbloat.net>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Starlink] [Rpm] RFC: bufferbloat observability project
Date: Sun, 12 Mar 2023 13:22:15 -0700 [thread overview]
Message-ID: <26f882c6-1b5a-412a-8e86-da990eb42426@rjmcmahon.com> (raw)
In-Reply-To: <CAA93jw76NJ+-acQiA+3JZs9HJjj4UgpReOOi8oGLWtGTe9gK=Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
Hi Dave,
Thanks for the mention of iperf 2. I want to clarify that the tooling over the last many years has a focus on ultra low latency both in metrics and mechanisms. Bufferbloat is supported mostly as a rating through the use of synthetic traffic and Little's Law. David Reed had pointed out that synthetic traffic does not match real world traffic, which comes from chaotic distributions and might be infinite in the possibilities (though maybe less than infinity squared.)
Bob
On Mar 12, 2023, 5:52 AM, at 5:52 AM, Dave Taht via Rpm <rpm@lists.bufferbloat.net> wrote:
>I just put together a list of common tools developers use every day,
>that would benefit from observing and managing network latency better.
>Things like git, and so on. Could some folk out there please pitch in
>with additional suggestions?
>
>https://docs.google.com/document/d/1SPuDhjMggexUuIGV8lUziQ3r8JjyLSwpZPoHieVLiaE/edit#heading=h.fyd7g5rbur4a
>
>Also it increasingly bothers me to see unbounded queues in so many new
>language libraries.
>
>--
>Roy Beatty (from Blade Runner) and I:
>https://www.understandinglatency.com/
>Dave Täht CEO, TekLibre, LLC
>_______________________________________________
>Rpm mailing list
>Rpm@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/rpm
[-- Attachment #2: Type: text/html, Size: 1567 bytes --]
prev parent reply other threads:[~2023-03-12 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 12:52 [Starlink] " Dave Taht
2023-03-12 20:22 ` Robert McMahon [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=26f882c6-1b5a-412a-8e86-da990eb42426@rjmcmahon.com \
--to=rjmcmahon@rjmcmahon.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=rpm@lists.bufferbloat.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