New issue
Advanced search Search tips

Issue 874874 link

Starred by 1 user
Status: Duplicate
Merged: issue 872172
Owner:
chrishtr@chromium.org
Closed: Aug 21
Cc:
tdres...@chromium.org
chrishtr@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

56% regression in rendering.mobile at 580453:581514

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

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

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

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


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

android-nexus5x-perf
Project Member

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

Cc: chrishtr@chromium.org
Owner: chrishtr@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14c0f214640000

Only invalidate property trees and compositing for PaintLayers when needed, on style change. by chrishtr@chromium.org
https://chromium.googlesource.com/chromium/src/+/ba8c87a1a32815e6061b7c38d31ddfbbaac7a124
9.483 → 14.61 (+5.129)

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

Comment 4 by chrishtr@chromium.org, Aug 21

Mergedinto: 872172
Status: Duplicate (was: Assigned)
►

Sign in to add a comment