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

Issue 920389 link

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



Sign in to add a comment

18.5% regression in blink_perf.parser at 620215:620219

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

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

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

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


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, Jan 9

Cc: chromium...@skia-public.iam.gserviceaccount.com
Status: Assigned (was: Unconfirmed)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/178c71c5940000

Roll AFDO from 73.0.3662.0_rc-r1 to 73.0.3663.0_rc-r1 by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/cb494102ab73c46eb0bcc3b49f8a1e4c6bbeb015
textarea-parsing: 8243 → 6692 (-1551)

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

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

Sign in to add a comment