Issue metadata
Sign in to add a comment
|
webrtc.datachannel performance metric should trace throughput. |
||||||||||||||||||||||||
Issue descriptionThe webrtc.datachannel test: https://chromeperf.appspot.com/report?sid=ad0063d8d8b7abc659ebda793837a94d1e5f4edeb739f58fce4bc126b3d01736 runs a datachannel for 30 seconds at full blast and checks how much CPU it uses. The more interesting metric is how much data it manages to move in 30 seconds; this should be relatively simple to measure.
,
Dec 1 2016
hbos@: can you take a look? maybe this is something that can be addressed by the new stats work.
,
Dec 1 2016
This sounds like something we can track with RTCDataChannelStats.bytes_sent/received in the perf test I'm working on[1] for the new getStats API. Merging this issue into perf test issue. This would fix it for the future getStats, but it would not fix it for the current perf test that you referenced in the bug description. Feel free to re-open if you want that too. [1] https://codereview.chromium.org/2545553003/ |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by manoranj...@chromium.org
, Nov 29 2016