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

Issue 903778 link

Starred by 1 user
Status: Assigned
Owner: ----
Cc:
█ chromium...@skia-public.iam.gserviceaccount.com
█ alexclarke@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.6%-88.7% regression in rasterize_and_record_micro.top_25 at 606421:606464

Project Member Reported by alexclarke@chromium.org, Nov 9 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 9 

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

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


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

linux-perf

rasterize_and_record_micro.top_25 - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 9

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/15f63a40140000

Roll AFDO from 72.0.3602.0_rc-r1 to 72.0.3605.2_rc-r1 by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/19ab1de37d7888fec318cce4b97437e46cb3f175
rasterize_time: 7.933 → 15.91 (+7.978)

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

Benchmark documentation link:
  None
►

Sign in to add a comment