Add tracing to measure the entire time it takes to satisfy a getStats request.

Add tracing to measure the entire time it takes to satisfy a getStats request.

BUG=369796
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=274220

[tommi (sloooow) - chröme, 2014-06-02 10:00:10]

ping in case you missed this.

[no longer working on chromium, 2014-06-02 11:03:20]

lgtm with one question, please remove the old trace event if it does not add
value any more.

https://codereview.chromium.org/306923008/diff/1/content/renderer/media/rtc_p...
File content/renderer/media/rtc_peer_connection_handler.cc (right):

https://codereview.chromium.org/306923008/diff/1/content/renderer/media/rtc_p...
content/renderer/media/rtc_peer_connection_handler.cc:243:
TRACE_EVENT0("webrtc", "StatsResponse::OnComplete")
do we still need this TRACE_EVENT0?

[tommi (sloooow) - chröme, 2014-06-02 11:27:48]

https://codereview.chromium.org/306923008/diff/1/content/renderer/media/rtc_p...
File content/renderer/media/rtc_peer_connection_handler.cc (right):

https://codereview.chromium.org/306923008/diff/1/content/renderer/media/rtc_p...
content/renderer/media/rtc_peer_connection_handler.cc:243:
TRACE_EVENT0("webrtc", "StatsResponse::OnComplete")
On 2014/06/02 11:03:21, xians1 wrote:
> do we still need this TRACE_EVENT0?

Yes, this one is still valuable.  It covers the callback as well, so it
currently is good to have to understand which portions of the wall-clock-time
have to do with adding reports and which have to do with calling into blink.

[tommi (sloooow) - chröme, 2014-06-02 11:27:52]

The CQ bit was checked by tommi@chromium.org

[commit-bot: I haz the power, 2014-06-02 11:28:47]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/tommi@chromium.org/306923008/1

[commit-bot: I haz the power, 2014-06-02 13:12:17]

Change committed as 274220