New issue
Advanced search Search tips

Issue 874914 link

Starred by 1 user
Status: Fixed
Owner:
yiyix@chromium.org
Closed: Aug 28
Cc:
sadrul@chromium.org
tdres...@chromium.org
yiyix@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

13.1%-15.2% regression in rendering.desktop at 581782:581854

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=874914

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


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

mac-10_13_laptop_high_end-perf
Project Member

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

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/1296cdca640000

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

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

Comment 4 by yiyix@chromium.org, Aug 21

Cc: sadrul@chromium.org

Comment 5 by yiyix@chromium.org, Aug 21 

It looks like it didn't cause any regression on any other metrics, ex: frame times. I will just monitor this issue for now.

Comment 6 by yiyix@chromium.org, Aug 27 

I will keep it beta to take some measurement, then i will revert it before stable cut for M69.

Comment 7 by yiyix@chromium.org, Aug 28

Status: Fixed (was: Assigned)
The cl is reverted here: https://chromium-review.googlesource.com/c/chromium/src/+/1194685

closing the bug
►

Sign in to add a comment