diff options
author | jsaji <52266412+jsaji@users.noreply.github.com> | 2020-05-01 16:16:18 +0300 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-05-01 16:16:18 +0300 |
commit | e68e59dfa93949605fdbed52fbbbef0d9f633edb (patch) | |
tree | 0d3b82132d31c00f414eb82368fd7f38e749e136 /README.md | |
parent | 9b62eaa704bade1907ddb51b50690b8c03234f32 (diff) | |
parent | aa09e1c38a89b4d4a9c3b6018c97d3efcfdebfe0 (diff) |
Merge branch 'master' into readme_fixes_2
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 7 |
1 files changed, 4 insertions, 3 deletions
@@ -58,9 +58,10 @@ Still a call creates a load on the participants' browsers (decoding streams) and 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. This means: - * on a desktop/laptop system, use a 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. - * on mobile device, use the Android/iOS app because mobile browsers will run out of computing power quickly. -* each participant disables video. + * on a desktop/laptop system, a browser like Firefox or Chrome should be used. The WebRTC implementation in other browsers is often sub-par. On a laptop, the power cord should be plugged in - this often results in better CPU performance. + * on mobile devices, the Android/iOS apps should be used because mobile browsers will run out of computing power quickly. +* all participant disables their video streams. + With this setup, 20 users should be possible in a typical setup. |