Skip to content

Comment on Jitsi Architecture – legacy desktop application (2011)

Comments

Here's the Jitsi architecture: https://i.imgur.com/oDSRzF4.png

Screen grabbed from their excellent tutorial videos: https://jitsi.org/news/tag/tutorial/

One thing we’ve found in deploying Jitsi several times is that good performance is difficult to achieve across parties who are across the globe.

We have some of our team in Armenia, Belarus and London and not all of then get consistent performance.

I know you can do geographic sharding so all EU or US guests get connected to their closest server but is there a way to ensure cross country participants all get good performance?

You can either:

- have the SFU (videobridge) in a more "central" location

- have multiple videobridge installations (cascaded bridges) where required with a low latency interconnect (its effectively a smart relay).

- you could use geographically distributed forced TURN servers with low latency interconnect to the SFU, but it would be more bandwidth intensive, and not really useful unless you truly have a REALLY low latency interconnect.

----------

Reducing the quality of the streams may also help, if it is bandwidth that is the constraining factor.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.