New issue
Advanced search Search tips

Issue 696519 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jul 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

100% improvement in browser_tests at 452598:452613

Project Member Reported by terelius@chromium.org, Feb 27 2017

Issue description

Performance change caused by the following CL: https://codereview.webrtc.org/2716683002

The CL has already been reverted and the metrics are back to their original level.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=696519

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghPeRpgoM


Bot(s) for this bug's original alert(s):

chromium-webrtc-trunk-tot-rel-linux

Comment 2 by tommi@chromium.org, Feb 27 2017

Thanks Bjorn.

I reverted the CL temporarily since it turns out we have some spinning loops in our code that start eating up too much CPU with the change.  I'm in the process of fixing them, already fixed two - maybe you can help me with this one? https://bugs.chromium.org/p/webrtc/issues/detail?id=7255
I still busy triaging other perf regressions, but I asked Philip to take a look at it in the meantime.

Comment 4 by tommi@chromium.org, Mar 14 2017

Labels: -M-58 M-59

Comment 5 by tommi@chromium.org, Jul 18 2017

Status: WontFix (was: Assigned)

Sign in to add a comment