New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 827132 link

Starred by 2 users
Status: WontFix
Owner:
zmo@chromium.org
Closed: Mar 2018
Cc:
piman@chromium.org
ccameron@chromium.org
█ kraynov@chromium.org
zmo@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.4% regression in system_health.common_desktop at 545409:545519

Project Member Reported by kraynov@chromium.org, Mar 29 2018 
See the link to graphs below.
Project Member

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

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

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


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

chromium-rel-mac11-pro
Project Member

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

Cc: zmo@chromium.org piman@chromium.org ccameron@chromium.org
Owner: zmo@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12be6d07440000

Enforce GPU earlier on Mac to avoid GPU switching during startup. by zmo@chromium.org
https://chromium.googlesource.com/chromium/src/+/ee6d9fdd6aa00ecc73a23d6da91425c3e776e498

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

Comment 4 by zmo@chromium.org, Mar 29 2018

Status: WontFix (was: Assigned)
This is expected since my CL switched Chrome from staring with Discrete GPU (incorrect GPU) to integrated GPU.
►

Sign in to add a comment