New issue
Advanced search Search tips

Issue 883738 link

Starred by 1 user
Status: Fixed
Owner:
yiyix@chromium.org
Closed: Sep 17
Cc:
npm@chromium.org
yiyix@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

55.2% regression in rendering.desktop at 585606:586992

Project Member Reported by npm@chromium.org, Sep 13 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 13 

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

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


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

Win 7 Nvidia GPU Perf

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 13

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/15830f85640000

Revert "FrameMetrics: Adding frame metrics analysis to LayerTreeHostImpl" by yiyix@chromium.org
https://chromium.googlesource.com/chromium/src/+/f898a23c1af094b58ea748c74948049893c08084
0.04995 → 0.09286 (+0.04291)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

Comment 4 by yiyix@chromium.org, Sep 17

Status: Fixed (was: Assigned)
The improvement was from "FrameMetrics: Adding frame metrics analysis to LayerTreeHostImpl" and the regression is from "Revert "FrameMetrics: Adding frame metrics analysis to LayerTreeHostImpl"". So no bug.
►

Sign in to add a comment