diff options
| author | simonspa <1677436+simonspa@users.noreply.github.com> | 2020-04-30 12:16:09 +0200 |
|---|---|---|
| committer | justinsaji <justinsaji1@gmail.com> | 2020-05-01 21:55:11 +1000 |
| commit | 9d1d81ce3285e4bc285e15e9e55a0bf046815d0b (patch) | |
| tree | a0c6899e24675080f9d70a99ba112b8544aeecf0 /README.md | |
| parent | 43511ddde95fc9c404c9870fea9bd408ef0582e4 (diff) | |
Clarify scalabiliy section a bit
Signed-off-by: Simon Spannagel <simonspa@kth.se>
Signed-off-by: justinsaji <justinsaji1@gmail.com>
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 6 |
1 files changed, 4 insertions, 2 deletions
@@ -57,10 +57,12 @@ 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. On a laptop, plug in the power - this often results in better CPU performance. +* each participant has a fast enough system,this means + * On a desktop/laptop system, use a browser like Firefix 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. + * On mobile device, use the Android/iOS app because mobile browsers will run out of computing power quickly * each participant disables video -With this setup, 20 users should be doable in a typical setup. +With this setup, 20 users should be possible in a typical setup. ### Scaling beyond 5-20 users in a call |