From: "Bjørn Ivar Teigen" <bjorn@domos.no>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] One-page explainer for latency under load. Suggestions welcome!
Date: Fri, 3 Jun 2022 13:52:36 +0200 [thread overview]
Message-ID: <CAKf5G6LpbE1yb8a4Hi0Mb73B2qjO33PW5TXRK_XoHhH0LpB4WA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
I've written this one-page explainer for latency under load. The idea is to
get the main point across while requiring minimal effort from the reader.
Trying to strike a good balance between conciseness and correctness.
Would love your input, comments open in this google doc:
https://docs.google.com/document/d/1G2_vBF31VT3TK_Ly8QtAeLIFzXBhLskfM6Y597Zxeoo/edit?usp=sharing
Best regards,
--
Bjørn Ivar Teigen
Head of Research
+47 47335952 | bjorn@domos.no <name@domos.no> | www.domos.no
[-- Attachment #2: Type: text/html, Size: 2195 bytes --]
next reply other threads:[~2022-06-03 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 11:52 Bjørn Ivar Teigen [this message]
2022-06-15 14:33 ` Bjørn Ivar Teigen
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=CAKf5G6LpbE1yb8a4Hi0Mb73B2qjO33PW5TXRK_XoHhH0LpB4WA@mail.gmail.com \
--to=bjorn@domos.no \
--cc=bloat@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