New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 911598 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.7%-5.8% regression in rasterize_and_record_micro.top_25 at 612967:612971

Project Member Reported by toyoshim@chromium.org, Dec 4

Issue description

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

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


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

Android Nexus5 Perf
Android Nexus5X WebView Perf

rasterize_and_record_micro.top_25 - Benchmark documentation link:
  None
Cc: chromium...@skia-public.iam.gserviceaccount.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1205b4e2140000

Roll AFDO from 72.0.3626.0_rc-r1 to 73.0.3628.0_rc-r1 by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/850eb03b9839d163c4f9f71609620ed1b26eb2c9
rasterize_time: 18.66 → 19.72 (+1.064)

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

Benchmark documentation link:
  None

Sign in to add a comment