From: Dave Taht <dave.taht@gmail.com>
To: Sean DuBois <sean@pion.ly>
Cc: bloat@lists.bufferbloat.net, libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [Bloat] Easiest/most effective way to test software against adverse networks?
Date: Sat, 5 Aug 2023 10:56:24 -0700 [thread overview]
Message-ID: <CAA93jw6i2E961jj8NSmZoBmxH4GdasvpRzzDHeVTb0Lqnry2Gw@mail.gmail.com> (raw)
In-Reply-To: <CA+b7xQtNzc9KQhvX5HPWReD4bEWSQQ5g427tg8CbusrVrM8GvA@mail.gmail.com>
GREAT to hear from you sean! (I added you as "accept" to the bloat
list, but did not subscribe you. You can subscribe if you want to stay
on) I am delighted to see all the places pion is popping up now, most
recently I hear it is in matrix´s stacked SFU implementation? That is
a very interesting case of multiple control loops, that makes my head
hurt.
We have very few tests for videoconferencing performance in the world
today. I have no idea how good any of the ones I have heard of, are.
Have you looked over what the FCC uses? Samknows? Cloudflare? Do you
have one or more you like?
This paper that just went by was quite pleasing:
https://tma.ifip.org/2023/wp-content/uploads/sites/12/2023/06/tma2023-final37.pdf
But I do not know enough about their method.
I have been hoping, with the public testbeds the libreqos project
runs, and/or with the co-operation of one or more of the ISPs that use
it, to somehow be able to accurately test & simulate the behaviors of
videoconferencing traffic, but someone with funding, interest and
time, has not shown up yet. (we know it is superlative, as most calls
about videoconferencing problems just vanish on deployment of
libreqos)
We are able now (via ebpf) to gather and analyze all sorts of stats at
scale, and substitute different qdiscs like fifo or pie, than the ones
(fq_codel, cake) we use in production. We do not have a good wifi or
lte emulation however.
So you are welcome to attempt to leverage our testbed for your
analyses or setup your own. The source code for libreqos is on github.
The main server has a demo here: https://payne.taht.net - click
"bandwidth test", drill down - but is only testing greedy and
voip-like traffic in the test suite, presently.
I am passionately interested in further understanding how well google
congestion control is working in the field today, as well as in other
videoconferencing methods. Please feel free to also drop by in the
chat:
https://matrix.to/#/#libreqos:matrix.org
On Sat, Aug 5, 2023 at 10:37 AM Sean DuBois via Bloat
<bloat@lists.bufferbloat.net> wrote:
>
> 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?
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Podcast: https://www.youtube.com/watch?v=bxmoBr4cBKg
Dave Täht CSO, LibreQos
next prev parent reply other threads:[~2023-08-05 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 17:35 Sean DuBois
2023-08-05 17:56 ` Dave Taht [this message]
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=CAA93jw6i2E961jj8NSmZoBmxH4GdasvpRzzDHeVTb0Lqnry2Gw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=libreqos@lists.bufferbloat.net \
--cc=sean@pion.ly \
/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