New issue
Advanced search Search tips

Issue 826827 link

Starred by 1 user
Status: Duplicate
Merged: issue 827145
Owner:
chiniforooshan@chromium.org
Closed: Apr 2018
Cc:
jam@chromium.org
npm@chromium.org
chiniforooshan@chromium.org
oysteine@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

30.6%-670.5% regression in system_health.common_desktop at 545919:546065

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

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

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

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


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

chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
linux-release
Project Member

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

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

Fix startup tracing in renderers by chiniforooshan@chromium.org
https://chromium.googlesource.com/chromium/src/+/f192e8a25e1937336d9cc16f9273b1d13b99530a

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

Comment 4 by chiniforooshan@chromium.org, Apr 24 2018

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

Sign in to add a comment