Zoom needs this API for the Zoom PWA & Web Client

[fideltian]

Hello, we have a web client and PWA version of zoom client. we love to have these kind of features very much. Some use cases i would like to share:

1. To give the better user experience, we could adaptor the vidoe resolution depends on the CPU occupation, especially the initial resolution. But due to privacy, we cannot get the cpu spec. So CPU occupation is also a way. Audio also have similiar use cases as video.
   2) we have some funny features, some of them need lots of computing load. we need to know the CPU occupation and decide the minimal machines to be supported.

And we looked at the APIs we have some feedbacks.

1. The observer mode will return the cpuUtilizationThresholds every 1 second. how about returning only when there is change. otherwise the callback is too often.
2. and provide a API that could be querid by Application at any time. it is to let application to adjust based on the up/down trend of CPU usage.

Another requirement is about implementation.

1. we would like the api could be workable even if the tab is inactive or minimized. We have a use case about desktop sharing.
2. the API could be workable in worker thread as well?

[kenchris]

@fideltian Thanks for the support for this API and the use-cases. I have opened up separate issues for the use-cases/feature requests that I could extract.

But I don't understand what you mean with the following

nd provide a API that could be querid by Application at any time. it is to let application to adjust based on the up/down trend of CPU usage.

Could you elaborate? Like I understand the request, but not the use-case

[fideltian]

Thanks kenchris. My original concern is the CPU usage might have some spike in the middle, which will impact the observers/logic. we would like to get the realtime cpu usage and do smooth algorithm to avoid a sudden spike. But i remember someone mentioned that the real cpu data is related with privacy?
we re-think of the current observer mode, based on that, we still could do some smooth algorithm to reduce the shorten spike of cpu usage. Then it should work as well.