New issue
Advanced search Search tips

Issue 814132 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.6% regression in loading.desktop at 536607:536668

Project Member Reported by yhirano@chromium.org, Feb 21 2018

Issue description

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=814132

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


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

chromium-rel-win8-dual
Project Member

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

Cc: toyoshim@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14dfa917840000

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
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