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

Issue 814178 link

Starred by 1 user
Status: WontFix
Owner:
yhirano@chromium.org
Closed: May 2018
Cc:
yhirano@chromium.org
█ alexclarke@chromium.org
toyoshim@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

15.5%-23.9% regression in system_health.common_desktop at 536603:536742

Project Member Reported by alexclarke@chromium.org, Feb 21 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Feb 21 2018 

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

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


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

chromium-rel-win10
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-nvidia
win-high-dpi
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Feb 21 2018

Cc: toyoshim@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/12d5c257840000

ResourceLoadScheduler: Count the number of throttlable requests by yhirano@chromium.org
https://chromium.googlesource.com/chromium/src/+/392731364d805ab0ee42e785382f23e0707f9f9a

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

Comment 5 by 42576172...@developer.gserviceaccount.com, Feb 22 2018 

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

Comment 8 by alexclarke@chromium.org, Feb 22 2018 

I started a pair of bisects to see if this really is https://chromium.googlesource.com/chromium/src/+/392731364d805ab0ee42e785382f23e0707f9f9a
Project Member

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

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

ResourceLoadScheduler: Count the number of throttlable requests by yhirano@chromium.org
https://chromium.googlesource.com/chromium/src/+/392731364d805ab0ee42e785382f23e0707f9f9a

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

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

📍 Found a significant difference after 1 commit.
https://chromeperf.appspot.com/job/14947aef840000

ResourceLoadScheduler: Count the number of throttlable requests by yhirano@chromium.org
https://chromium.googlesource.com/chromium/src/+/392731364d805ab0ee42e785382f23e0707f9f9a

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

Comment 11 by yhirano@chromium.org, May 14 2018

Status: WontFix (was: Assigned)
I'd like to close this issue as WONTFIX because the change is net neutral for performance, according to the finch result. See https://docs.google.com/document/d/1oreWB98RmEhqGIM9vQgOs9s7llBLxHsxubhNyN8Cmrg/edit for details.
►

Sign in to add a comment