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

Issue 876370 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
█ farahcharab@google.com
lanwei@chromium.org
altimin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

14.7%-168.1% regression in rendering.mobile at 580453:581514

Project Member Reported by lanwei@chromium.org, Aug 21 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 21 

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

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


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

Android Nexus5 Perf
android-nexus5x-perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 22

Cc: farahcharab@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12c0be52640000

Scheduler: Extend resource fetch priority experiment to loading only. by farahcharab@google.com
https://chromium.googlesource.com/chromium/src/+/bac05e51eb8937e213689a3e190acd697467eef6
60.05 → 173 (+112.9)

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

Comment 4 by ricea@chromium.org, Aug 28

Components: Blink>Scheduling Blink>Loader
Status: Available (was: Assigned)
►

Sign in to add a comment