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

Issue 868899 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jul 31
Cc:
sunn...@chromium.org
█ pmeenan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.7%-161.3% regression in rendering.mobile at 577212:578091

Project Member Reported by pmeenan@chromium.org, Jul 30 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 30 

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

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


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

Android Nexus5 Perf

Comment 3 by pmeenan@chromium.org, Jul 31

Status: WontFix (was: Untriaged)
New benchmark (noisy).
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Aug 2

Cc: sunn...@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/148fc2eba40000

Reland "cc: Throttle incoming begin frames in scheduler" by sunnyps@chromium.org
https://chromium.googlesource.com/chromium/src/+/1607d9124b4df6bf0175c3ec69b7aef6a981ddb6
18.29 → 43.3 (+25.02)

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

Sign in to add a comment