What is the performance impact of running webrtc-issue-detector in a prod environment? #15
-
We're thinking of implementing this as a means to detect slow networks in our WebRTC app and was wondering what the performance impact is, especially on slow/older devices or devices that are under heavy load due to other tasks/apps running at the same time |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Hi @kelvin2200 ! Actual performance impact depends on the amount of RTP senders/receivers, as long as getStats() is executed for each of them (for those with media tracks enabled). |
Beta Was this translation helpful? Give feedback.
-
thank you @evgmel |
Beta Was this translation helpful? Give feedback.
Hi @kelvin2200 ! Actual performance impact depends on the amount of RTP senders/receivers, as long as getStats() is executed for each of them (for those with media tracks enabled).
You could measure the impact on a slow/older device with & without of WID library with your app layout / consumed tracks to understand the difference on the specific device/context.
In our roadmap checklist there is such line:
Adaptive getStats() call interval based on last getStats() execution time
. That's what will be useful in cases when we understand that the statistics was not parsed/analysed for the expected time interval.But if you implement it, you can always open a PR. Any useful changes are welcome!