About CPU usage improvements
As stated by @michael_p.zoom (replied here) :
For instance, the High CPU usage issue is dependent on Chrome releasing the WebAssembly SIMD feature for Chrome 84 on July 14th. This helps drastically reduce the CPU usage for meetings. We are still performing internal testing to make sure the SIMD feature meets Zooms standard, once we’re finish testing we will release a new version.
CPU usage should drastically be reduced. I was really happy to see that announcement since we face some difficulties when users run Zoom Web SDK on low CPU spec machines.
Our expectation were big, as our deception after testing. CPU usage remain the same (high and bursting as hell)
Let’s be clear, just enabling the SIMD support and upgrading to the latest Chrome version is not enough. It also depends on how the encoder has been implemented.
Here are my questions:
- what did you change on the encoder to support and use SIMD capacities ?
- how can we monitor the improvement compare to let say version 1.7.10 without SIMD support ?
- could you describe what how CPU is used in the Web SDK ? (use as many threads as you can, use only 1 thread for video encoding but full resources without any pause, etc.)