New issue
Advanced search Search tips

Issue 820776 link

Starred by 1 user
Status: WontFix
Owner:
g...@chromium.org
Closed: Mar 2018
Cc:
g...@chromium.org
agrieve@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

16.1% improvement in blink_perf.bindings at 534413:534499

Project Member Reported by g...@google.com, Mar 11 2018 
Playing with the Bisect button. In particular, I want to see if the AFDO profile update is why we're seeing this improvement. Please ignore if CC'ed.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Mar 11 2018 

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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=a98c8fca4d553754226a3e0ed305b891174188ce7b4a5aa9ce22049ad673e7e7


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

android-one
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 11 2018

Cc: agrieve@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11501d1a440000

[AFDO] Roll Android's profile to 66.0.3336.3_rc-r1 by gbiv@chromium.org
https://chromium.googlesource.com/chromium/src/+/d07b07609f7b538fdbb09f6c06ccba20218f2e9b

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 4 by g...@chromium.org, Mar 11 2018

Status: WontFix (was: Assigned)
Excellent. That means I can probably blame  issue 814162  on this.
►

Sign in to add a comment