From: Sean DuBois <sean@pion.ly>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] Easiest/most effective way to test software against adverse networks?
Date: Sat, 5 Aug 2023 13:35:40 -0400 [thread overview]
Message-ID: <CA+b7xQtNzc9KQhvX5HPWReD4bEWSQQ5g427tg8CbusrVrM8GvA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 267 bytes --]
I am working on improving Pion's Google Congestion Control algorithm
https://github.com/pion/interceptor/tree/master/pkg/gcc. As I start to use
it in more real world networks I find flaws.
How are people testing software today? Is 'Traffic Control' the best option?
[-- Attachment #2: Type: text/html, Size: 396 bytes --]
next reply other threads:[~2023-08-05 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 17:35 Sean DuBois [this message]
2023-08-05 17:56 ` Dave Taht
2023-08-05 19:30 ` Stephen Hemminger
2023-08-05 19:54 ` Dave Taht
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=CA+b7xQtNzc9KQhvX5HPWReD4bEWSQQ5g427tg8CbusrVrM8GvA@mail.gmail.com \
--to=sean@pion.ly \
--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