4e7aa43ea0
We have two histograms today that trigger on large jumps in either platform reported stream delays (WebRTC.Audio.PlatformReportedStreamDelayJump) or the system delay in the AEC (WebRTC.Audio.AecSystemDelayJump). The latter is the internal buffer size in the AEC. The sizes of such jumps are of relevance since it can harm the AEC and even put it in a complete failure state. It is hard, not to say impossible, to tell how frequent it is. Therefore, two complementary histograms are added; number of jumps in each metric. This way we get a quick way to determine how often a jump occurs in general and also how frequent it is within a call. This is solved by adding a counter for each metric. The counter is activated either upon an event trigger or if we know for sure when the AEC is running. Unfortunately, we can't rely on the destructor at the end of a call so we add a public API for the user to take on the action of calling it at the end of a call. Tested locally by building ToT chromium including changes and three triggered jumps (200, 50 and 60 ms). The stats picked up the 60 and 200 ms jumps as expected. BUG=488124 R=asapersson@webrtc.org, pbos@webrtc.org Review URL: https://codereview.webrtc.org/1229443003. Cr-Commit-Position: refs/heads/master@{#9544} |
||
|---|---|---|
| .. | ||
| app/webrtc | ||
| build | ||
| examples | ||
| media | ||
| session/media | ||
| codereview.settings | ||
| COPYING | ||
| libjingle_examples.gyp | ||
| libjingle_media_unittest.isolate | ||
| libjingle_p2p_unittest.isolate | ||
| libjingle_peerconnection_unittest.isolate | ||
| libjingle_tests.gyp | ||
| libjingle.gyp | ||
| LICENSE_THIRD_PARTY | ||
| OWNERS | ||
| PRESUBMIT.py | ||