diff options
| author | Jos Poortvliet <jospoortvliet@gmail.com> | 2020-04-06 09:05:07 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-04-06 09:05:07 +0200 |
| commit | 782cb740f08e3a6c3dd498fee0670e0d67a24c42 (patch) | |
| tree | fe74953de5f51cb673f2feb5f9305efdd6e64b6f /README.md | |
| parent | ab9a6c3af3608f2c46f3795428dc663839383838 (diff) | |
Update README.md
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -37,7 +37,7 @@ Here's a short [video](https://youtu.be/KdTsWIy4eN0) on how it's done. ## Scalability -Talk works peer to peer, that is, each participant sends an end-to-end encrypted stream to each other participant and receives one stream per other participant. This grows bandwidth usage with the number of participants. As most users are on an asymetric local internet connection, the sending bandwidth often becomes the bottleneck. A typical Nextcloud Talk instance can handle a few dozen calls, but each call can have only 4-6 participants with video depending on the participants' bandwidth. Without video, more is possible. +Talk works peer to peer, that is, each participant sends an end-to-end encrypted stream to each other participant and receives one stream per other participant. This grows bandwidth usage with the number of participants. A single video stream currently uses about 1 mbit/sec and the total required bandwidth can be calculated as follows: @@ -57,7 +57,7 @@ Still a call creates a load on the members' browsers (decoding streams) and on t To make sure a call can sustain the largest number of participants, make sure that: * each participant has a fast upload and download -* each participant has a fast enough system (desktop/laptop browser, mobile device browsers will run out of computing power quickly) or uses the Android/iOS app. Best use a desktop browser like Firefox or Chrome. The WebRTC implementation in other browsers is often sub-par. +* each participant has a fast enough system (desktop/laptop browser, mobile device browsers will run out of computing power quickly) or uses the Android/iOS app. Best use a desktop browser like Firefox or Chrome. The WebRTC implementation in other browsers is often sub-par. On a laptop, plug in the power - this often results in better CPU performance. * each participant disables video With this setup, 20 users should be doable in a typical setup. |