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

Issue 814181 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

37.7% regression in loading.desktop at 536658:536696

Project Member Reported by alexclarke@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=814181

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


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

chromium-rel-win7-gpu-intel
Project Member

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

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

Comment 5 by 42576172...@developer.gserviceaccount.com, Feb 22 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/11852517840000

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)
There are two regressions, but both were improved by my previous change[1] before this regression, so they are not real regressions. 

1: https://chromium.googlesource.com/chromium/src/+/1f25bbc692f06964b5e10c7312f9f81377cdea32

Sign in to add a comment