New issue
Advanced search Search tips

Issue 875984 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Aug 28
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

16.3% regression in rendering.mobile at 581549:582144

Project Member Reported by hjd@google.com, Aug 20

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=875984

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


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

Android Nexus5 Perf
Cc: yiyix@chromium.org
Owner: yiyix@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16e21311640000

FrameMetrics: Adding frame metrics analysis to LayerTreeHostImpl by yiyix@chromium.org
https://chromium.googlesource.com/chromium/src/+/808c1f33139afdc7d32b838938ed297a3f27f8f1
38.35 → 44.68 (+6.333)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
I will keep it beta to take some measurement, then i will revert it before stable cut for M69. 
The cl is reverted here: https://chromium-review.googlesource.com/c/chromium/src/+/1194685

closing the bug
Status: Fixed (was: Assigned)

Sign in to add a comment