DescriptionImplement UMA and internal data structure for tracking EWOULDBLOCK.
There are currently 2 sources of EWOULDBLOCK. One is from the system which we don't have any monitoring in place. The other is generated by the socket implementation of WebRTC. This change adds UMA for both places. The UMAs added here are
1. max consecutive EWOULDBLOCK that we receive from the system. It's protocol dependent.
2. max consecutive EWOULDBLOCK that WebRTC socket generates. Protocol independent.
3. % of packet loss in WebRTC socket layer due to its own EWOULDBLOCK generation. Protocol independent.
Tested in a call and the dtor is invoked when a call is terminated. However, if a user just closes the renderer abruptly, the dtor is not invoked such that these UMA data points will be lost.
BUG=427555
Committed: https://crrev.com/fd669ae63f860c24399867d79dcbcca528c13b6f
Cr-Commit-Position: refs/heads/master@{#301575}
Patch Set 1 #
Total comments: 10
Patch Set 2 : #
Total comments: 10
Patch Set 3 : #
Total comments: 2
Patch Set 4 : #
Total comments: 10
Patch Set 5 : #
Total comments: 5
Patch Set 6 : #
Total comments: 14
Patch Set 7 : #
Messages
Total messages: 25 (5 generated)
|