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

Issue 903169 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 905162
Owner:
Closed: Nov 27
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.3%-35.8% regression in rendering.desktop/tasks_per_frame_total_all at 604760:604825

Project Member Reported by alexclarke@chromium.org, Nov 8

Issue description

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

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


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

linux-perf
mac-10_12_laptop_low_end-perf

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/16e92f0de40000
Cc: oysteine@google.com
Owner: oysteine@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/114a93e3e40000

Perfetto: Fix for worker threads not finalizing proto packets by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/d420ce980291dbdee3d8a68594afbbfe5b75fbb4
thread_total_all_cpu_time_per_frame: 8.089 → 8.572 (+0.4834)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Mergedinto: 905162
Status: Duplicate (was: Assigned)

Sign in to add a comment