New issue
Advanced search Search tips

Issue 841244 link

Starred by 2 users
Status: Duplicate
Merged: issue 836469
Owner:
lukasza@chromium.org
Closed: Nov 26
Cc:
lukasza@chromium.org
primiano@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

8% regression in loading.desktop at 552587:552602

Project Member Reported by primiano@google.com, May 9 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, May 9 2018 

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

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


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

win-high-dpi
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 13 2018

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

Make --site-per-process the default on ToT via fieldtrial_testing_config by lukasza@chromium.org
https://chromium.googlesource.com/chromium/src/+/fb1ccf02ee8ca79e1404abfd3a3a7d540b7d2dbd

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

Comment 4 by lukasza@chromium.org, Nov 26

Mergedinto: 836469
Status: Duplicate (was: Assigned)
►

Sign in to add a comment