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

Issue 913785 link

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



Sign in to add a comment

40.7%-74.6% regression in rendering.desktop/thread_total_all_cpu_time_per_frame at 615053:615066

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

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

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

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


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

linux-perf

rasterize_and_record_micro.top_25 - Benchmark documentation link:
  None

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Project Member

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

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/14a124a6140000

Roll AFDO from 73.0.3635.0_rc-r1 to 73.0.3636.0_rc-r1 by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/4b05c21182e9ab5715389b016ae38a67484281d7
rasterize_time: 8.566 → 16.55 (+7.988)

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

Benchmark documentation link:
  None
►

Sign in to add a comment