General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Rpm <rpm@lists.bufferbloat.net>,
	 Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] RFC: bufferbloat observability project
Date: Sun, 12 Mar 2023 05:52:16 -0700	[thread overview]
Message-ID: <CAA93jw76NJ+-acQiA+3JZs9HJjj4UgpReOOi8oGLWtGTe9gK=Q@mail.gmail.com> (raw)

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

             reply	other threads:[~2023-03-12 12:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12 12:52 Dave Taht [this message]
2023-03-12 20:22 ` [Bloat] [Rpm] " Robert McMahon

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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw76NJ+-acQiA+3JZs9HJjj4UgpReOOi8oGLWtGTe9gK=Q@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --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