From: Sean DuBois <sean@siobud.com> To: Luca Muscariello <muscariello@ieee.org> Cc: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>, galene@lists.galene.org Subject: [Galene] Re: [Bloat] testing latency under load on webrtc with galene? Date: Thu, 4 Mar 2021 11:09:27 -0800 [thread overview] Message-ID: <YEEwZy7eoIJn9Z7u@SeanLaptop.sioBuD.com> (raw) In-Reply-To: <CAH8sseQ-vGYJdrj+6mmz++L2MrQ4SvfEh4Ja49Tx_mTUVXJG2w@mail.gmail.com> I would really love to build a general WebRTC tester. Spinning up lots of Chromium instances is super expensive. Even if you do the mock webcam you are doing way more then needed. I created[0] which spins up many PeerConnections to load test a server. I think this would be a great alternative to the testing that exists today. * You can send pre-encoded video or RTP packets directly. * You can receive RTP and not pay the costs of processing * You get direct access to Receiver Reports, Transport Wide Congestion Control and Receiver Estimated Max Bandwidth. * Way easier to deploy. We can build a small static binary. If anyone is interested would love to help them kick off a project. We can make it general enough to test Galene, Janus, Jitsi, Ion etc... If it gets acceptance from the greater WebRTC community it could really grow! [0] https://github.com/pion/rtsp-bench/blob/master/client/main.go On Tue, Mar 02, 2021 at 05:01:42PM +0100, Luca Muscariello wrote: > Dave, > > we have done extensive WebRTC (and several other online meeting > apps) testing lately and this paper > https://ieeexplore.ieee.org/document/9153228 reports a > methodology for WebRTC based on Chromium and Selenium Grid and > as test orchestrator Jitsi Torture. > > I would avoid feeding clients with BBB as video as it is not > representative of a meeting as encoders are optimized for > different kinds of video. There are several video samples > out there. > > We have scaled up clients to hundreds with this methodology. > The paper is short so many details have been omitted but there > are not many other options to do this kind of test at scale. > > Luca > > > > > > > > describes the methodology > > > > On Tue, Mar 2, 2021 at 2:15 AM Dave Taht <dave.taht@gmail.com> wrote: > > > Given that we have a worldwide network of flent servers... > > > > Given how easy galene is to hack on... and a 10 minute install... > > > > given some webrtc scripting... a few more stats... some javascript... > > skull sweat... funding... > > > > It seems plausible to be able to construct a suite of tests that could > > indeed track jitter > > delay and loss across the internet over webrtc. Perpetually uploading > > bigbuckbunny or some > > other suitable movie might be an option, but I have a fondness for > > extracting a sub 30 second segment from "Max Headroom", which if > > those here have not seen it, predicted much of the fine mess we're all > > in now. > > > > I guess my question is mostly, is a "headless" test feasible? In the > > context of samknow's lack of webrtc test... lowpowered hw.... > > > > -- > > "For a successful technology, reality must take precedence over public > > relations, for Mother Nature cannot be fooled" - Richard Feynman > > > > dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729 > > _______________________________________________ > > Bloat mailing list > > Bloat@lists.bufferbloat.net > > https://lists.bufferbloat.net/listinfo/bloat > > > _______________________________________________ > Galene mailing list -- galene@lists.galene.org > To unsubscribe send an email to galene-leave@lists.galene.org
next prev parent reply other threads:[~2021-03-04 19:09 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-02 1:14 [Galene] " Dave Taht 2021-03-02 14:59 ` [Galene] " Jeroen van Veen 2021-03-02 16:01 ` [Galene] Re: [Bloat] " Luca Muscariello 2021-03-04 19:09 ` Sean DuBois [this message] 2021-03-04 21:22 ` Luca Muscariello
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.galene.org/postorius/lists/galene.lists.galene.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=YEEwZy7eoIJn9Z7u@SeanLaptop.sioBuD.com \ --to=sean@siobud.com \ --cc=bloat@lists.bufferbloat.net \ --cc=dave.taht@gmail.com \ --cc=galene@lists.galene.org \ --cc=muscariello@ieee.org \ --subject='[Galene] Re: [Bloat] testing latency under load on webrtc with galene?' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox