Nils, Thank you for clarification.
I need a tool that uses near the same client code that our WebRTC javascript client has. First I was really going to implement it with the use of C++ and some Node.js + WebRTC native compatible lib, but I was unsuccessful to find such a mix which would be really working. Making the Frankenstein myself is too big task for just a some load testing tool. I guess I have to migrate to Chromium with this task. On Thursday, November 24, 2016 at 12:28:27 AM UTC+3, Nils Ohlmeier wrote: > Hi Alexander, > > > On Nov 23, 2016, at 08:55, Alexander Abagian wrote: > > > > We've made a WebRTC load testing js app, starting a set of WebRTC clients > > in a single page. Each of them has it's own RTCPeerConnection and > > everything other. > > > > When it starts from Firefox, then only 15 of these clients become > > connected. Any extra clients are dead. > > > > It looks like there is some limitation for ICE entities. Could you point me > > the way to look at ? > > I look at it from the point that Firefox was and is not designed to be (ab-) > used as a load testing tool/client. > > 15 PeerConnections would be a really big conference call and you probably hit > all kind of internal limitations. > If you are serious about building a WebRTC load testing tool I would > recommend you to not do it in JS, but instead build your own client in C++ or > something like that. > > Best > Nils Ohlmeier _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
