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 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 CTO, TekLibre, LLC Tel: 1-831-435-0729 > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat >