New issue
Advanced search Search tips

Issue 808645 link

Starred by 1 user
Status: Fixed
Owner:
cbiesin...@chromium.org
Closed: Feb 2018
Cc:
npm@chromium.org
cbiesin...@chromium.org
asvitk...@chromium.org
chrishtr@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.6%-8.7% regression in thread_times.key_silk_cases at 532586:532818

Project Member Reported by npm@chromium.org, Feb 2 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Feb 2 2018 

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

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


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

android-nexus5
android-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Feb 3 2018

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

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

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

Comment 4 by vmi...@chromium.org, Feb 5 2018

Components: Internals>GPU>Metrics

Comment 5 by cbiesin...@chromium.org, Feb 8 2018

Status: Fixed (was: Assigned)
reverted in https://crrev.com/772b2bcdbaa8ea5c5b1f47255c6c1562016fb680

Comment 6 by cbiesin...@chromium.org, Feb 8 2018 

er, rather, the revert just restored the original performance
►

Sign in to add a comment