New issue
Advanced search Search tips

Issue 868996 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Aug 3
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

11.2% regression in blink_perf.svg at 578948:578948

Project Member Reported by pmeenan@chromium.org, Jul 30

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=868996

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


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

Android Nexus6 WebView Perf
Owner: g...@chromium.org
Status: Assigned (was: Untriaged)
Assigning to sheriff gbiv@chromium.org because this autoroll is the only CL in range:
Roll AFDO from 70.0.3505.0_rc-r1 to 70.0.3506.0_rc-r1

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file a bug against
gbiv@chromium.org. Additional context:  https://crbug.com/805539 

The AutoRoll server is located here: https://afdo-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=gbiv@chromium.org

Change-Id: I45de9bb3d758307b16787c6b9d8b35bf9ef62e7d
Reviewed-on: https://chromium-review.googlesource.com/1154437
Commit-Queue: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#578948}
Cc: -pmeenan@chromium.org
Ack; will watch and see what future rolls to do this.

For context, AFDO profiles are generated by sampling Chrome's execution and feeding that back into the compiler, so the compiler can better optimize Chrome. This process is inherently noisy, so we'll sometimes see benchmarks that are highly sensitive to certain optimizations being performed (read: many of blink's benchmarks) swing around from time to time, and we’ll sometimes see Chrome vary in size as the inliner decides to be more/less aggressive. Denoising this is being tracked in issue 849881.
Status: Fixed (was: Assigned)
Appears to have recovered. 

Sign in to add a comment