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

Issue 804308 link

Starred by 1 user
Status: Fixed
Owner:
yhirano@chromium.org
Closed: Apr 2018
Cc:
yhirano@chromium.org
█ pmeenan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

10.1%-35.9% regression in system_health.common_desktop at 529265:529722

Project Member Reported by pmeenan@chromium.org, Jan 22 2018 
See the link to graphs below.
Project Member

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

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

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


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

chromium-rel-mac11-air
win-high-dpi
Project Member

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

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

Update RendererSideResourceScheduler testing config (Enabled_3_1024)
By yhirano@chromium.org · Wed Jan 17 06:00:00 2018
chromium @ e6395d1c63e9f382fbd13de8bc94796712fd88b2

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

Comment 4 by isherman@chromium.org, Jan 22 2018

Cc: -isherman@chromium.org
Project Member

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

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/1481e9ae840000
Project Member

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

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14e6f776840000

[DO NOT COMMIT] Revert 3_1024 by yhirano@chromium.org
https://chromium-review.googlesource.com/c/chromium/src/+/890697/1

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

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

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16eaea36840000

[DO NOT COMMIT] 3_1024 => 1_1024 by yhirano@chromium.org
https://chromium-review.googlesource.com/c/chromium/src/+/895237/1

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

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

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16add9a6840000

[DO NOT COMMIT] 3_1024 => 2_1024 by yhirano@chromium.org
https://chromium-review.googlesource.com/c/chromium/src/+/895107/1

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

Comment 13 by yhirano@chromium.org, Feb 7 2018 

--
Project Member

Comment 16 by 42576172...@developer.gserviceaccount.com, Feb 7 2018 

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12825999840000

[DO NOT COMMIT] disabled => 3_1024 by yhirano@chromium.org
https://chromium-review.googlesource.com/c/chromium/src/+/905963/1

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

Comment 17 by 42576172...@developer.gserviceaccount.com, Feb 7 2018 

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

Comment 18 by yhirano@chromium.org, Apr 2 2018 

I reverted the change.

Comment 19 by yhirano@chromium.org, Apr 2 2018

Status: Fixed (was: Assigned)
►

Sign in to add a comment