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

Issue 913589 link

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



Sign in to add a comment

14.1% regression in blink_perf.parser at 614629:614645

Project Member Reported by npm@chromium.org, Dec 10 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 10 

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

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


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

linux-perf

blink_perf.parser - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 10

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/12fb4dd2140000

Roll AFDO from 73.0.3632.0_rc-r1 to 73.0.3633.0_rc-r1 by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/c799ff4c01ee578954c86e82739593b8d461e8a5
textarea-parsing: 7991 → 6778 (-1213)

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

Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks
►

Sign in to add a comment