New issue
Advanced search Search tips

Issue 808646 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.1% regression in thread_times.tough_compositor_cases at 532631:532719

Project Member Reported by npm@chromium.org, Feb 2 2018

Issue description

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

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


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

linux-release
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/12e2488e840000
Components: Internals>GPU>Metrics
Cc: cbiesin...@chromium.org chrishtr@chromium.org asvitk...@chromium.org
Owner: cbiesin...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/13c66071840000

Revert "Add UKM metrics for rendering timing measurements" by cbiesinger@chromium.org
chromium @ 772b2bcdbaa8ea5c5b1f47255c6c1562016fb680

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Owner: ----
The revert just got things back to the previous state
Status: WontFix (was: Assigned)

Sign in to add a comment