New issue
Advanced search Search tips

Issue 806756 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac , Fuchsia
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.1%-5% regression in speedometer at 532067:532142

Project Member Reported by tebbi@chromium.org, Jan 29 2018

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 29 2018

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

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


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

chromium-rel-win10
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Jan 29 2018

๐Ÿ“ Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14c5bada840000
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 29 2018

Cc: haraken@chromium.org palmer@chromium.org
Owner: palmer@chromium.org
๐Ÿ“ Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14c5bada840000

Enable the Oilpan metadata canary in production builds.
By palmer@chromium.org ยท Fri Jan 26 23:13:26 2018
chromium @ 129fac28f2fc2e9003222a0be60997f299841a9a

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Cc: fdoray@chromium.org thestig@chromium.org thomasanderson@chromium.org dpranke@chromium.org
 Issue 807261  has been merged into this issue.
Cc: primiano@chromium.org asvitk...@chromium.org cbiesin...@chromium.org xidac...@chromium.org chrishtr@chromium.org
 Issue 806794  has been merged into this issue.
 Issue 806832  has been merged into this issue.
Cc: awhalley@chromium.org jsc...@chromium.org
Labels: OS-Chrome OS-Fuchsia OS-Linux OS-Mac OS-Windows
Status: WontFix (was: Assigned)
I think we have to accept this performance cost in the interest of safety.
I concur with palmer@'s assessment.

Sign in to add a comment