- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Jun 2017 08:28:49 +0000
- To: public-webrtc-logs@w3.org
I don't understand what is being proposed here. As for having per-frame stats, measuring various parts of the pipeline, that might make sense to do here if aggregate values are of interest, but it does not make sense to do getStats or the like on a per-frame basis, that is infeasible for performance. Performance and frame-sensitive information should be exposed with a different API. The referenced blink-dev discussion talks about end-to-end latency. We've talked about exposing that in getStats in #158 and #222. Further offline discussions have not brought us a solution to estimating this yet. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/119#issuecomment-306132570 using your GitHub account
Received on Monday, 5 June 2017 08:28:55 UTC