New issue
Advanced search Search tips

Issue 902753 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

8.3%-13% regression in system_health.common_mobile at 604386:604590

Project Member Reported by lanwei@chromium.org, Nov 7

Issue description

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

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


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

android-nexus5x-perf

system_health.common_mobile - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
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/16499049e40000

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

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

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

Sign in to add a comment