using your latest web SDK 1.7, we are getting very high CPU loads on our platforms.
This was acceptable on our ‘stronger’ models, but is very bad on our ‘low-end’ model
(nevertheless a 4x core Intel cpu i3-7100U CPU @ 2.40GHz), as video / audio begins stuttering
and/or A/V is out of sync
the zoom application is basically the only application running on the machine, occupying the CPU
most of the time.
if muting VIDEO from the local side (where we see the performnace problems / high cpu load), we receive audio / video in acceptable quality and delay (between audio/video)
suspecting from the WASM section of your API description: preLoadWasm() and also by observing GPU load(which is not changing when starting up zoom JS), we suspect that you do all the en/decoding in JS?
also: using the ‘normal’ browser based webapp in chromium 78 (i.e. the non-JS SDK client), the platform in question delivers sufficient audio/video quality and delay.
- Is there any possibility to improve this, by e.g. using different webassemblies, restricting resolution, …?
- are there plans to improve this performance issue in an upcoming JS SDK version?
- switch to chromium based en/decoding, instead of JS code?