New issue
Advanced search Search tips

Issue 902066 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

9.3% regression in media.desktop at 604494:604516

Project Member Reported by jrumm...@chromium.org, Nov 5

Issue description

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

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


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

mac-10_13_laptop_high_end-perf

media.desktop - Benchmark documentation link:
  None
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/11003155e40000
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/17989685e40000

Perfetto: Fix for worker threads not finalizing proto packets by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/d420ce980291dbdee3d8a68594afbbfe5b75fbb4
cpu_time_percentage: 0.4188 → 0.4478 (+0.029)

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

Benchmark documentation link:
  None
Mergedinto: 902072
Status: Duplicate (was: Assigned)

Sign in to add a comment