4 ms·

Browsers do generally have a limit on simultaneous outgoing connections per domain[1] - it could be related to that. (This is also why e.g. TFS breaks down when

• kelnos 6y ago
  I doubt that has anything to do with it. Zoom almost certainly handles composing the image for gallery view server-side; you're not maintaining a separate connection for each participant.
  • msie 6y ago
    I thought i read somewhere that they don’t, which is what makes them more performant.
  • jessaustin 6y ago
    It's possible that the server just forwards a selection of packets from each participant (hopefully dropping some from those who aren't speaking or moving) and the client stitches them into the view.
    • kelnos 6y ago
      Sure, that would be the SFU doing it's job, but my point is that you aren't maintaining a connection per participant, but one connection with Zoom itself where you get all the video data. It's true that could be in the form of a single video stream of the entire gallery, or separate streams of only the participants visible to you.
  • londons_explore 6y ago
    Google Meet does send each video participants video stream seperately. You can tell this by disconnecting internet and then clicking a (now frozen) participant - they become fullscreen but low-res. That means the client must have had that data locally rather than needing to wait for the server to send it.
• kyberias 6y ago
  Do you happen to know why TFS causes this? Does it leave connections open in each tab? Otherwise it should not matter how many tabs we have open I think.