New issue
Advanced search Search tips

Issue 901457 link

Starred by 1 user
Status: Duplicate
Owner:
oysteine@google.com
Closed: Nov 2
Cc:
oysteine@google.com
dougman@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

29%-75.7% regression in media.mobile at 604455:604514

Project Member Reported by dougman@chromium.org, Nov 2 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 2 

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

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


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

android-nexus5x-perf

media.mobile - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 2

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/11fc6409e40000

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

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

Benchmark documentation link:
  None

Comment 4 by oysteine@chromium.org, Nov 2

Mergedinto: 901458
Status: Duplicate (was: Assigned)
►

Sign in to add a comment