Live data from Hacker News

Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

webrtchacks.com

51–60 of 115 posts

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#51

Earlier quoted context omitted.

The Jistsi team says the server needs roughly 5.5Mbps per Chrome user. Firefox uses a lot more bandwidth, system resources, and degrades the room capacity. Just something to keep in mind, and after some testing I saw the same results. My AWS bill was projected to be over $1k/month, so I put it on Linode where it'll cost between $100-200/month. Just about any decent VPS provider would be good options compared to AWS d…

Is there cheaper bandwidth available than Hetzner's 1.19euro +vat per TB? (Linode seems to be at 10$ / TB).

Or Hetzners dedicated hosts that have zero cost for bandwidth and unlimited traffic as well, haven't been able to find anything cheaper than that.

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#52

It's a fantastic open source solution. Can be self hosted. It is to note that traffic does go through the server, hence need decent bandwidth. the server afaik does have the keys to decrypt traffic

The Jistsi team says the server needs roughly 5.5Mbps per Chrome user. Firefox uses a lot more bandwidth, system resources, and degrades the room capacity. Just something to keep in mind, and after some testing I saw the same results. My AWS bill was projected to be over $1k/month, so I put it on Linode where it'll cost between $100-200/month. Just about any decent VPS provider would be good options compared to AWS d…

> The Jistsi team says the server needs roughly 5.5Mbps per Chrome user.

That sounds like a lot! I wonder why an almost still image can use that much bandwidth, I guess it has to do with the low-latency requirement but I would love more details on that.

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#53

We did our daily standup call with it yesterday (mostly audio). 12 people, on a $3 Scaleway Debian instance (2GB RAM). Worked perfectly. Obviously as we stopped using Zoom we have to manually upload all our personal data to Facebook now.

> Obviously as we stopped using Zoom we have to manually upload all our personal data to Facebook now. I feel like there is a joke that's going over my head or I simply don't understand. Why you have to manually signup/login/auth/whatever with Facebook because you're using Jitsi now, especially on your own host?

That is the joke. :)

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#54

We did our daily standup call with it yesterday (mostly audio). 12 people, on a $3 Scaleway Debian instance (2GB RAM). Worked perfectly. Obviously as we stopped using Zoom we have to manually upload all our personal data to Facebook now.

> Obviously as we stopped using Zoom we have to manually upload all our personal data to Facebook now. I feel like there is a joke that's going over my head or I simply don't understand. Why you have to manually signup/login/auth/whatever with Facebook because you're using Jitsi now, especially on your own host?

... because Zoom isn't doing it automatically anymore?

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#55

We did our daily standup call with it yesterday (mostly audio). 12 people, on a $3 Scaleway Debian instance (2GB RAM). Worked perfectly. Obviously as we stopped using Zoom we have to manually upload all our personal data to Facebook now.

> Obviously as we stopped using Zoom we have to manually upload all our personal data to Facebook now. I feel like there is a joke that's going over my head or I simply don't understand. Why you have to manually signup/login/auth/whatever with Facebook because you're using Jitsi now, especially on your own host?

The joke is that zoom was found to be sending user info to Facebook apis.

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#56

Something that isn't mentioned in the docs is room (and server) capacity, or at least rough estimates. The Jitsi team gave some specific numbers on room capacity in the forums. Each room should reliably handle 20-35 Chrome users (Firefox uses roughly double the resources), and has a cap at 75. Apparently if you're only using audio, then rooms of 70+ people will work fine. They're working on upping this number to 500…

Where does the difference between Chrome and Firefox come from? Is Firefox using a different video format?

See here for details: https://github.com/jitsi/jitsi-meet/issues/4758

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#58
Alternatives to Jitsi are Janus (mentioned in this thread) but also OpenVidu (formerly Kurento) and Mediasoup which provide building blocks to roll your own. All of these also have demos that you can use out of the box for our own conferences.

Re: Jitsi Meet – Improving Scale and Media Quality with Cascading SFUs (2018)

#60

Something that isn't mentioned in the docs is room (and server) capacity, or at least rough estimates. The Jitsi team gave some specific numbers on room capacity in the forums. Each room should reliably handle 20-35 Chrome users (Firefox uses roughly double the resources), and has a cap at 75. Apparently if you're only using audio, then rooms of 70+ people will work fine. They're working on upping this number to 500…

Unfortunately from my experience, Jitsi does not reliably handle 20-35 users
Post reply on HN