New issue
Advanced search Search tips

Issue 888399 link

Starred by 1 user
Status: Assigned
Owner: ----
Cc:
kouhei@chromium.org
uwyiming@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.8%-28.8% regression in rendering.desktop at 591048:591297

Project Member Reported by kouhei@google.com, Sep 24 
See the link to graphs below.
Project Member

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

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

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


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

Win 7 Perf

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

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

Cc: uwyiming@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/144fa9df640000

Reintroduce the DidCommitAndDrawCompositorFrame event. by uwyiming@google.com
https://chromium.googlesource.com/chromium/src/+/0f8836c2f30926602691d6a38c799b77c3194585
0.1069 → 0.1246 (+0.0177)

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

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

Sign in to add a comment