New issue
Advanced search Search tips

Issue 911964 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.3%-17.6% regression in system_health.common_desktop at 603864:606971

Project Member Reported by toyoshim@chromium.org, Dec 5

Issue description

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

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


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

Win 7 Nvidia GPU Perf
Win 7 Perf

system_health.common_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

power.desktop - Benchmark documentation link:
  https://bit.ly/power-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/14f88c3c140000

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

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

Sign in to add a comment