Issue 649314 link

Starred by 2 users

Issue metadata

Status:	WontFix
Owner:	terelius@chromium.org
Closed:	Dec 2016
EstimatedDays:	----
NextAction:	----
OS:	----
Pri:	2
Type:	Bug-Regression
Performance M-55

4.2%-13.4% regression in browser_tests at 419366:419429

Project Member Reported by terelius@chromium.org, Sep 22 2016

Issue description

It looks like CPU usage and frame count regressed on the 17th but recovered on the 19th. This suggests a CL that was reverted, but I can't find any good candidate in the blame lists.

Comment 1 by terelius@chromium.org, Sep 22 2016

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=649314

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgmZ_lxgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgudf6sgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghYjutgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-byJvQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-ZrDpAoM


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

chromium-webrtc-trunk-tot-rel-linux

Comment 2 by rbyers@chromium.org, Nov 18 2016

Labels: Performance

Comment 3 by terelius@chromium.org, Dec 7 2016

Status: WontFix (was: Assigned)

►

Issue 649314 link

Issue metadata

4.2%-13.4% regression in browser_tests at 419366:419429

Issue description

Comment 1 by terelius@chromium.org, Sep 22 2016

Comment 1 Deleted

Comment 2 by rbyers@chromium.org, Nov 18 2016

Comment 2 Deleted

Comment 3 by terelius@chromium.org, Dec 7 2016

Comment 3 Deleted

Sign in to add a comment