New issue
Advanced search Search tips

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

226.8% regression in media.desktop at 603928:604493

Project Member Reported by liberato@google.com, Nov 30

Issue description

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

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


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

Win 7 Nvidia GPU Perf

media.desktop - Benchmark documentation link:
  None
Cc: oysteine@chromium.org oysteine@google.com
Owner: oysteine@google.com
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/15b3d648140000

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@chromium.org
https://chromium.googlesource.com/chromium/src/+/3bb24369bef996b43b2d2711f0033ba472f779ea
buffering_time: 10.8 → No values

Perfetto: Fix for worker threads not finalizing proto packets by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/d420ce980291dbdee3d8a68594afbbfe5b75fbb4
buffering_time: No values → 28.08

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

Benchmark documentation link:
  None

Sign in to add a comment