Description of changes:
Frames per second of video stream was being processed on the main thread using setTimeout. However, when a meeting window gets moved into the background, the main thread timer used in setTimeout gets throttled and the fps drops dramatically. To overcome this issue, this PR will move the setTimeout call into a worker thread that does not get throttled.
Testing:
Can these tested using a demo application? Please provide reproducible step-by-step instructions.
Yes, start a meeting with at least one other attendee. Enable a video filtered and then hide the window (switch tabs). The other attendee should then observe no fps degradation in filter-enabled attendee.
Checklist:
Have you successfully run npm run build:release locally?
yes
Do you add, modify, or delete public API definitions? If yes, has that been reviewed and approved?
no
Do you change the wire protocol, e.g. the request method? If yes, has that been reviewed and approved?
no
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Issue #:
Description of changes: Frames per second of video stream was being processed on the main thread using setTimeout. However, when a meeting window gets moved into the background, the main thread timer used in setTimeout gets throttled and the fps drops dramatically. To overcome this issue, this PR will move the setTimeout call into a worker thread that does not get throttled.
Testing:
Can these tested using a demo application? Please provide reproducible step-by-step instructions. Yes, start a meeting with at least one other attendee. Enable a video filtered and then hide the window (switch tabs). The other attendee should then observe no fps degradation in filter-enabled attendee.
Checklist:
Have you successfully run
npm run build:releaselocally? yesDo you add, modify, or delete public API definitions? If yes, has that been reviewed and approved? no
Do you change the wire protocol, e.g. the request method? If yes, has that been reviewed and approved? no
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.