New issue
Advanced search Search tips

Issue 808641 link

Starred by 1 user
Status: WontFix
Owner: ----
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.4%-4.5% regression in thread_times.tough_compositor_cases at 532680:532795

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=808641

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


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

chromium-rel-win7-dual
chromium-rel-win7-x64-dual
Project Member

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

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/12526bce840000

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

Components: Internals>GPU>Metrics
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Feb 6 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/14ae0171840000

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

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

Comment 7 by cbiesinger@google.com, Feb 7 2018

Owner: ----
This isn't my change

Comment 8 by chrishtr@chromium.org, Feb 7 2018

Status: WontFix (was: Assigned)
The drop and increase are both correlated with the patch that was reverted, so no
net change. Closing.
►

Sign in to add a comment