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

Issue 813946 link

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



Sign in to add a comment

26.1% regression in loading.desktop at 536611:536669

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

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

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

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


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

chromium-rel-win10
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/16c89057840000

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 4 by yhirano@chromium.org, Feb 21 2018

Cc: ksakamoto@chromium.org
Status: WontFix (was: Assigned)
According to ksakamoto@ cpuTimeToFirstMeaningfulPaint_avg itself is not a optimization target, so I am closing this bug.
►

Sign in to add a comment